Echo JS 0.11.0

Ha, you're beginning to sound like Sean Larkin and I bet this kind of attitude will make even the "asset bundling community" suffer really soon. You both brag about the tool you maintain in a way that sounds like this all the time: "hey, good job newcomer, but don't forget I'm way better than you and I'll repeat as much as I can, I'll even ignore how old each of the tools compared are! I think competition is good but don't say my tool is not the best ok?". Stop that, even core maintaners of JS UI libs stopped that, having options is awesome (I don't mean that there should be only one bundler) but just stop being passive-agressive like that, you're hurting people that are new to web dev.

Upvoted, as I have been interested in the project for a while. But recently with the release of Parcel.js, I would like an update on FuseBox unique value proposition. It seems to me that if I am going to go with another non-trivial configuration-based bundler, I might as well choose Webpack.

Thanks!
I will be posting benchmarks and comparison soon. Parcel.js claims to be "blazing fast", but that's not true. 2s seconds for HMR compared to 50ms in FuseBox. That's for starters.

Zero config - not true either. People are still forced to configure it using package.json

FuseBox is more flexible in many ways. Parcer.js doest's have tree shaking, FuseBox does it even on es5 code, and the algorithm is unique + Fuse does code optimisation making the output super light. I've just scratched the surface ;-)

So Parcel.js developer and the developers that wrote https://medium.freecodecamp.org/all-you-need-to-know-about-parcel-dbe151b70082 that has > 7.5K claps are falsely promoting Parcel?

Parcel.js will eventually have tree shaking, as that is not some proprietary magic trick, in fact, it's plain stupid that not all bundlers share the same logic that enables tree shaking.

What do you mean by FuseBox algo being unique? I'm just curious.

And what do you mean by making the output super light? What's the difference with e.g., rollup?

That's for the next article!

"People are still forced to configure it using package.json" > what are you talking about ?

Well, if you need your CSS handled like you want for example. How about setting some plugins for PostCSS, configuring Sass (with parcel you do it using package.json),  If you are building a large project you will need configs, sooner or later. How about aliases? I stop now ;-)

then you are configuring PostCSS and Sass, but parcel itself is zero config. I think Fusebox could learn a lot from the #0cjs trend, just like webpack did with v4

Zero config is good for getting started, but a large project needs some solid configuration.

https://github.com/fuse-box/fuse-box/blob/master/docs/release3.0.md