Dompack - tools and components to build sites in a ES7/IE11+ world
Dompack expects to be integrated into your website using WebPack & Babel.
dompack-builder can
do this for you but usually you'll be using dompack together with the
WebHare CMS
import * as dompack from 'dompack';
`Using dompack outside WebHare
If you intend to ship published files, you amy only need it as a dev-dependency
`
npm i --save-dev dompack dompack-builder
echo '{ "build": { "entrypoint": "site.es" }}' > dompack.json
node_modules/.bin/dompack-builder -r . # add '-w' to watch
`And add something like this to your pages
`
``Both frameworks also ship with their own event implementations, requiring anyone
integrating with these libraries (and components built on it) to register with
those event systems. Native events are easier to integrate with.
Mootools (not sure about jquery) stores its event listeners in a global storage,
which makes it hard to actually get DOM nodes to be garbage collected.
Multiple instances of mootools (not sure about jquery) which may happen with
iframes, can collide with each other and get confused about 'slick ids'...
jQuery builds a parallel API to the DOM, learning you things the jQuery-way
that nowadays have a perfectly usable DOM-way, which gets in the way if the
site you're working on doesn't include or expose a jQuery object. We liked
the mootools approach of always letting you work with the native DOM objects
and DOM api.
There are good reasons for these issues (and most of them point back to old
browsers or the leaking DOM implementations of IE) but we needed a clean start.