In your layout you might have something like the following..
If you are using express, you would configure your app and add Mixr's routes
var Mixr = require'mixr';appconfigure'development'MixraddExpressRoutesapp;;
Then, by default, Mixr will look for ./assets/css/app.css, ./assets/js/app.js and render that file using a syntax similar to sprockets
in app.css ..
/**= require bootstrap.min.css*/
in app.js ..
//= require jquery.min.js$// do something..;
When you require something, it is looked for in the same directory, but you can also specify a path..
Although Mixr is very fast at generating the output files, it is just a waste of CPU etc to generate the assets on every request.
Therefor in production mode, it is recommended to generate the assets to a public folder and have either Nginx, Node, etc to server them normally..
Mixr will come with a command line utility to perform this task in future, probably with S3 upload ability..
Mixr is designed to be quite modular, in the future, planned I have the following.
- Expanded files in development mode for easier debugging
- Integrating images and generating cacheable images, including inputting base64 input css.
- Allow any kind of processor to be done to a file, by using file extensions