How Ender bundles libraries for the browser
I was asked an interesting Ender question on IRC (#enderjs on Freenode) and as I was answering it, it occurred to me that the subject would be an ideal way to explain how Ender's multi-library bundling works. So here is that explanation!
The original question went something like this:
When a browser first visits my page, they only get served Bonzo (a DOM manipulation library) as a stand-alone library, but on returning visits they are also served Qwery (a selector engine), Bean (an event manager) and a few other modules in an Ender build. Can I integrate Bonzo into the Ender build on the browser for repeat visitors?
Wait, what's Ender?
Let's step back a bit and start with some basics. The way I generally explain Ender to people is that it's two different things:
$('selector').method(). The constituent libraries provide the functionality for the methods and may also provide the selector engine functionality.
Continue reading this article on DailyJS.com