Re:Browserify vs. Webpack – Configuration isn't evil
by Confiks on Monday July 27, 2015 @04:50PM
(#9957909)
Thanks for mentioning JSPM/System.js. It's really cool; it runs ES6 compilation with Babel (or Traceur) in the browser, and is able to download arbitrary versions of dependencies off a CDN.
I'm still fiddling a bit with hotloading React and caching source files, but it looks promising.
Re:Browserify vs. Webpack – Configuration isn't evil
by Offler on Monday July 27, 2015 @04:17PM
(#9957732)
npm is getting its house in order when it comes to browser package management. I wouldn't bet too heavily on something else.
Re:Browserify vs. Webpack – Configuration isn't evil
by lewisl9029 on Monday July 27, 2015 @08:09PM
(#9958816)
JSPM has fairly seamless support for loading libraries from npm, Github, local Git repos in any format (global, CJS, AMD, ES6) as ES6 modules.
So you don't need to bet on any particular ecosystem.
If you're trying to decide between build systems I would recommend checking it out, and watching this video[2] for a nice overview.
[1] http://jspm.io [2] https://www.youtube.com/watch?v=iukBMY4apvI