Now just visit any
.js url which maps to a path under /public and the packaged file will be served.
debug options as true in production without impacting users but still benefiting from being able to obtain sourcemaps. Care should be taken to limit access to the mapfiles (served via the /path/to/original/js/script.map.json) usually with middleware before enchilada.
No one likes a stale enchilada. Out in the real world, you want to leverage browser caching for rarely changing files. Imagine that your project uses files like jquery or engine.io, these files don't change as much as your app code. It would be silly to keep sending them with every js file you serve up. Enchilada makes this easy to do.
Just add the proper ingredients and your enchilada will be served up as you requested.
Now just make sure you load the required scripts before any other js file that might use them.
<!-- load the scripts we know will be used by several files --><!-- load other js files as you would before -->
See the examples directory for working code you can copy and paste.
Install with npm
npm install enchilada