Then we can all eventually move forward from this mess of non-standard module formats and loaders.
import Vue from 'vue'
import jQuery from 'jquery'
global.jQuery = jQuery // to get the next line to
work
import Bootstrap from 'bootstrap'
import 'bootstrap/dist/css/bootstrap.css'
import became a giant "do something cool on this line" that maybe the tooling you're using knows how to translate via (say) a webpack loader.
For anyone wondering, that line gets translated to the browser dynamically including css on the page.
The way I typically thought of dependencies with browsers was to bundle them all together. Is there some new solution to this problem?
But to appropriate someone else's full exact name for another purpose is kind of rude – especially if that person makes their living from their public image/name.
"Johnny"
1. lazy-loads files
2. handles JS/CSS/images
3. handles nested dependencies
4. makes it easy to manage dependencies among team members
5. is extremely lightweight
When you use that, you have dependency management supported by the browser natively.
In that light, are custom dependency loaders still needed?
var exports = {};
function require(modname) {
if (modname == 'jquery') return $;
else if (modname.startsWith('.')) return exports;
else { console.log("Unknown require()", modname); return exports; }
}