Maybe you should name this JohnnyDep so it's more an allusion and less the actual person's name? Dep makes more sense anyways, as dependency has one p.
Hi Everyone - author here. I just wanted to give you some background on the project. JohnnyDepp came out of a feature request I got on another project called LoadJS (<a href="https://github.com/muicss/loadjs" rel="nofollow">https://github.com/muicss/loadjs</a>) which is an async loading library. The request was for a higher-level dependency manager that:<p><pre><code> 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
</code></pre>
I realize that many teams use RequireJS to manage dependencies but I saw an opportunity to make a library that could accomplish many of the same things but with a much smaller footprint and a simpler API. I hope you'll give it a try and let me know what you think!
Nothing beats my dependency manager, which I'll just call DrGonzo:<p><pre><code> var exports = {};
function require(modname) {
if (modname == 'jquery') return $;
else if (modname.startsWith('.')) return exports;
else { console.log("Unknown require()", modname); return exports; }
}
</code></pre>
(Of course you've gotta <include> the modules ahead of time -- I actually use this for <a href="http://8bitworkshop.com/" rel="nofollow">http://8bitworkshop.com/</a>)
Cool, reminds me of this [0], it's 850 chars before gzipping.<p>[0]: <a href="https://curiosity-driven.org/minimal-loader" rel="nofollow">https://curiosity-driven.org/minimal-loader</a>
Please no. Write standard modules. Serve standard modules to modern browsers, optionally bundling to modules for production. Bundle to non-modules for legacy browsers.<p>Then we can all eventually move forward from this mess of non-standard module formats and loaders.