Unbundle the http module?
See original GitHub issueWanted to get your thoughts on whether the http
module still makes sense to bundle with choo? As opposed to pointing folks to it in the readme as a “recommended” module. But if you don’t need to make http requests, it isn’t really relevant for you.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Browser module loading - can we stop bundling yet? - sgom.es
We're not dealing with the dependency issue in the unbundled versions yet, though; the browser still has to load each individual JS file...
Read more >unbundle - npm
Unbundle is designed for, for not limited to, delivering web apps with protocols like HTTP/2 Server Push. Other tools can be used to...
Read more >Using Native, Unbundled ES6 Modules With a Simple Build ...
HTTP /2 and caching help out a lot here, but the browser still has to request every single module before it can start...
Read more >Unbundling the JavaScript module bundler by Luciano ...
Codemotion Rome 2018 - Today we all use Webpack (right?), but I remember a time when you had to manually copy-paste JavaScript files...
Read more >Building without bundling: How to do more with less
Unbundled roadblock #1: Browsers don't yet support importing by package name (known as importing by “bare module specifiers”).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@timwis i think the intention behind bundling
xhr
withinchoo
aschoo/http
is forchoo
to be an opinionated grab-bag of what you need for common applications. since thechoo/http
module is separate from the top-levelchoo
module, if you don’t need to make http requests then you can choose to notrequire('choo/http')
and thus your bundle will not includexhr
, so the only penalty is the minimal time it took to installxhr
when you installedchoo
(which is not much sincexhr
is tiny). i personally like this approach of grab bag modules, but it is a slight departure from a pure “batteries not included” approach.Hah yeah, think it’s alright to keep it for now and close this then. If someone feels strongly about it discussion is def welcome, always welcome to reopen!