Centralized aster API.
Source maps are a great invention that is meant to simplify life by allowing developers to debug the original code (the one that they actually write, whatever language it is) on production.
However, using them is pretty hard in any of existing build systems whenever you have at least one plugin in your build pipeline - and you most likely do - that doesn't support emitting them or even consuming from previous step; some plugins even treat code as simple strings discarding all it's inner logic and structure.
Your code isn't just a string. It has a soul and rich inner world and aster is built to treat it like that. As result, it provides complex yet easy and fast transformations that are transparent for browser debugger out of the box.
You can think of aster for JS as of rework for CSS.
Definitely no! aster doesn't try to fight your favorite build system. It has only one specific area that it's exceptionally good at - code processing. Everything else (CSS, images, publishing to CDN, etc.) is left for generic builders, and you can use them together.
Currently there are following bindings:
If you wish, you can define aster pipeline as custom task in any existing build system on your own since aster uses RxJS under the hood, which is interoperable with events, streams, promises, callbacks and any other asynchronous primitives and patterns out of the box.
aster is completely modular and main package is just a centralized API wrapper for core parts published as separate modules (check out their documentations for details):
aster as a development dependency:
npm install --save-dev aster
Then, create build script and use it. Example (
aster doesn't provide task runner - npm is already good one, and we don't want to create one more bicycle. You can simply define every needed task as separate script, or use aster as part of existing builder as mentioned before.
Check out aster's Yeoman generator.
It automizes the process of creating basic skeleton and Github repo for your plugin in few easy steps. When created, you just need to modify
test.js files to reflect your intended plugin's functionality (detailed hints included right in code).