Echo JS 0.11.0

<~>
nchanged 2505 days ago. link parent 1 point ▲ ▼
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 ;-)

Replies

flickerz 2505 days ago. link 2 points ▲ ▼
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?
sylvainpv 2505 days ago. link 1 point ▲ ▼
"People are still forced to configure it using package.json" > what are you talking about ?
nchanged 2505 days ago. link 1 point ▲ ▼
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 ;-)
sylvainpv 2505 days ago. link 2 points ▲ ▼
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
nchanged 2505 days ago. link 1 point ▲ ▼
Zero config is good for getting started, but a large project needs some solid configuration.