Echo JS 0.11.0

Yet another datepicker control for react, no aria/accessibility attributes for the modal and menu, doesn't seem to be keyboard navigable at all.

Yeah, including a poorly written one from the same submitter a month ago.

Very cool... I was afraid this was a text content filter, which are generally very bad all around.

That said, I'm not sure a naked blue woman might not trigger the filter, while a couple of tan colored bowls might.  Automated content filtering often become more trouble than it's worth with many false positives and negatives respectively.

I'm still not sure I get why Bit is any more useful than just straight npm... I had similar feelings about Bower, which also had node+npm as a prerequisite.

On the client frameworks, one part bugged me a lot.

> Angular enables developers to build web, mobile or desktop-based applications

Angular doesn't enable this any more than any other web framework out there, and in some ways it can make it worse.

On the data layers, there's a few parts here, redux is a lot different than GraphQL/Apollo, which require a server complement.  Redux also requires sagas, thunks or similar to be roughly equivalent just on the client.  It's state management, not data management.

On the server-side, I mostly agree... Koa isn't that new though, it's my favorite abstraction as the extension model is imho better than alternatives, and I do wish it were better supported.  More devs have taken to Hapi for creating API services, which should probably have been mentioned.

Interesting... although I really do prefer Redux over the rxjs pipelines I can see why someone would like this better.  In the end, it feels like a huge library requirement for what you get from it.  Not to mention the Angular http client vs. axios, fetch or a number of other options.

Missing accessibility attributes for modal elements.

Interesting... I do use a bit of minimal DOM manipulation via refs with React the only real gotcha is handling mount, update and unmount events.  If the same component is on multiple screens during navigation, you need to handle update almost like mount, but account for already mounted events.

Examples: I'm client-rendering markdown into a react control, but want to handle routing to a /docs/* path in the application, so have a single event listener for click on the parent control to handle nested A elements.  Similarly I have instances where some minor SVG and mouse events trigger behaviors that don't work well in react directly.

I find the few times I need to extend a React component to use direct DOM access isn't so bad, just have to account for a few lifecycle events.  A lot of this came in the box, so to speak with jQuery which I've used as long as its' been around.

All of the above are of course better than the old west days of the v4 browser wars.

Pretty nifty... I'm kind of sad that e4x never got wide adoption, or that AS3 was never extended for good JSON support in the box... though seeing a binary representation is cool.  Curious how much it would take to work with the underlying typed array support in JS directly, since that could work in a browser and in node.

Also, not sure of the utility, given that flash/flex browser support is all but gone outside IE.

Lighthouse is built into chrome already - Developer Tools -> Audits -> Accessibility.

WAVE - https://wave.webaim.org/extension/

Axe - https://www.deque.com/axe/