Echo JS 0.11.0

In general, there are two major reasons to use DI.  The first is testability, as testing frameworks for TS/JS can override imports, that lessens the use case significantly.  The other is to easily target multiple plugins/modules that can be changed out.  If you aren't actively targeting multiple versions or plugin models, that lessens the second reason.

For most developers, most of the time, hard coding to an instance/module and using the testing frameworks to override those imports is less cumbersome than the overhead to reason with DI abstractions when spelunking through code in the future.

Wasn't there some risk of timing exploits for the earlier implementations?

Would be cool, but I don't think I've ever seen more than 3 downvotes on a post... 

I keep thinking it one had to have X karma in order to post...  but don't necessarily want to discourage first time posts.  The spammy accounts tend to be all over the map... some see about 3/4 quality post and 1/4 crap, others the inverse, others still single post, decent quality and others single post, crap.

Not to be negative, just feels like short of immense development, hand curation is still, largely the best option.

Mostly agree... I'd probably be more inclined to switch to typescript before adding an immutable library at this point.  And I'm not really doing ts in the app code.

Note: put .env in your .gitignore file... so it doesn't accidentally get checked into source control.

still prefer fetch/node-fetch directly.

Would add joi and ajv to the list, since they're more widely used than either.

Why is everything renamed to .txt?

This is not a "fix" it's a work around... if you actually want italics, it's still broken.  I can't speak to the source of the bug, but did you actually submit a support ticket or bug report to the Chrome developers?

As-demonstrated can only have a single emitter in a chain... there are no considerations for subscribing to event channels at all.