need time to think on how this would relate to https://github.com/dimich-g/webpackage/issues/26 …
our current thinking is that Service Worker does a lot of what we 1/
-
-
expected to need to make configurable via the loader, but not 2/
-
everything. So the platform would still have a configurable loader 3/
-
excellent - so loader s/b able to be configured to "just work" for npm resolution, right?
@BrendanEich@bradleymeck@justinfagnani -
what do you mean by npm resolution, exactly?
-
guess I should've said node resolution. npm i react; import 'react' and it works, natively
@wycats@bradleymeck@justinfagnani -
crawling up directories is never going to be a good idea in the browser
-
ofc not :) My point of ref is jspm - install from npm while *spitting out* loader config.
@BrendanEich@wycats@bradleymeck -
same w/ bundling - loader is told what bundles have which modules, where. Just curious 1/
@BrendanEich@wycats@bradleymeck - 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.