Echo JS 0.11.0

Ah, yes, I knew I saw something similar somewhere else:
http://codepen.io/hexagoncircle/pen/akWOdE
And it's just a pen.

Bundling them would break the asynchronicity behind import(), i.e. you're not lazy loading anything.

The purpose of lazy loading is to serve just the resources to make the page work and load everything else when needed in order to optimize the data that's being sent. If you bundle everything up, what are you even optimizing?

Only if you want a bundle that comprises every module you need.
But then again, import() will be used to load modules dynamically and *asynchronously*, so their place is actually *not* in such bundles, but in separate files that are lazy-loaded as needed.

Looks like Moment is incompatible with the mere existence of an object named `global`.

I'm so, so very disappointed in this.

Yeah that was my basic idea too. Thanks!

Are you of that party that thinks that every component could (and should) be defined like that?
I'm not React expert but I find it quite a stretch, because there are components that just need internal state, but it's too verbose/cumbersome/overkill to rely on Redux (or anything like that) for the case. Is there a best practice guide for that?

May I suggest not doing that? I mean, developers need a little stability. Semver is ok and all, but releasing 7 versions in two hours (incluing a minor one) makes me think it's a rushed release.

Instead, take a little more time, publish a more polished version when you're quite done. Bugs might still slip out, but it's no big deal to release a patch version shortly after.
*One* patch, though, not 6 *and* a minor upgrade.

V5.0.0 was released 2 hours ago and now it's already at v5.1.3?!

That was expected, sadly. It's not an easy task.

In the meanwhile, Node community might opt to use another extension to tell CommonJS and ES2015 modules apart. I really hope it won't happen.

Again, don't forget to add tests to your packages.