Echo JS 0.11.0

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.

That's the problem of not having tests: you should have noticed that in Firefox vendor-prefixed style properties begin with "Moz", not "moz".

Other suggestions:
- one could pass the perfectly valid property "font-smoothing", the function would have tried searching for "webkitFont-smoothing"... and failed, because it's "webkitFontSmoothing". So, camelCase the *whole* property, or make the documentation clearer that they should use "fontSmoothing" instead;
- it doesn't check for vendor-prefixed *values*, like "-ms-grid" for display. Unfortunately checking them isn't as easy, but that would be one of the perks of such a package. As it is, it's quite trivial and similar to many others (e.g.: https://www.npmjs.com/package/prefix-property).

Let me get this straight, I should use an Angular directive to style my layout?!