our current thinking is that Service Worker does a lot of what we 1/
-
-
Replying to @wycats @BrendanEich and
expected to need to make configurable via the loader, but not 2/
1 reply 0 retweets 0 likes -
Replying to @wycats @BrendanEich and
everything. So the platform would still have a configurable loader 3/
2 replies 3 retweets 4 likes -
Replying to @wycats
excellent - so loader s/b able to be configured to "just work" for npm resolution, right?
@BrendanEich@bradleymeck@justinfagnani1 reply 0 retweets 0 likes -
Replying to @AdamRackis @wycats and
what do you mean by npm resolution, exactly?
1 reply 0 retweets 0 likes -
Replying to @BrendanEich
guess I should've said node resolution. npm i react; import 'react' and it works, natively
@wycats@bradleymeck@justinfagnani2 replies 0 retweets 0 likes -
Replying to @AdamRackis @BrendanEich and
crawling up directories is never going to be a good idea in the browser
1 reply 0 retweets 1 like -
Replying to @justinfagnani
ofc not :) My point of ref is jspm - install from npm while *spitting out* loader config.
@BrendanEich@wycats@bradleymeck2 replies 0 retweets 0 likes -
Replying to @AdamRackis @justinfagnani
same w/ bundling - loader is told what bundles have which modules, where. Just curious 1/
@BrendanEich@wycats@bradleymeck1 reply 0 retweets 0 likes -
Replying to @AdamRackis @justinfagnani
if that's same direction native stuff is taking - sorry if stupid question!
@BrendanEich@wycats@bradleymeck1 reply 0 retweets 0 likes
the intent is config network layer via SW & perhaps a sync resolution hook at JS layer
-
-
Replying to @wycats @AdamRackis and
You mean sync but not doing i/o, ofc :-).
1 reply 0 retweets 1 like -
Replying to @BrendanEich @AdamRackis and
right. Just resolve (referrerURI, specifier) to targetURI
0 replies 2 retweets 3 likes
End of conversation
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.