> > You seriously made another module loader?
> Yeah. There are several reasons why:
> To create a new-feeling environment that is clearly not node,
> because you’re writing code that runs in node and IE9 and Chrome
> etc. It shouldn’t feel like any old node.js module.
Why shouldn't it feel like any old node.js module? Nearly all the work
in JS packaging of late has been to abstract the differences so that
we can use the well-established node packaging system on both ends.
We're already able to do it with stuff like babel and browserify.
[skit author here] -- skit handles CSS and multi-file module definitions (with submodules) in a novel way, that's probably more important to me than the reason you pasted.
Comments
[skit author here] -- skit handles CSS and multi-file module definitions (with submodules) in a novel way, that's probably more important to me than the reason you pasted.