Echo JS 0.11.0

One significant issue… no server-side rendering option without a separate dependency injection. This could be combined with the new Context if the Store in question were able to have separate instances, instead of a global/static reference.

My only comment is the restructuring really isn't a React thing, it can be used WITH React, but isn't technically IN React.  I find, that when training/mentoring junior/mid developers learning modern JS and React is that they will often conflate the two, when a given concept is learned with the React part, not knowing you can use it elsewhere in JS.

Just surprised it wasn't submitted already, at least I didn't see it...

One minor feature that might be nice would be a lookup, where you pass a URL and you get a matching route with route parameters back.

Nice... could be used, via history with connected router to automagically dispatch data loading against routes.

Could then use this paired with the new Context providers for route data...

mind... blown.

Came to say the exact same thing... for those reading, the latest Node versions already support async iteration against readable streams, which is so much cleaner than some other options.

Hmm... if only there were a site for this already... maybe with a comments section... maybe a similar UX to say hacker news, but specific to JS... oh yeah, we could call it Echo JS.

Don't do this, let the methods expire… we have async functions now… beyond async being a reserved word.

Obviously a place that doesn't have any/many over 30 or 40.

Would be better to use async functions.  Supported in all modern browser for quite a while as well as in node for several years.  Not to mention via Babel since before the name change (iirc).