Echo JS 0.11.0

Would add that username and password are not automatically decoded, use decodeURIComponent.

Probably the biggest benefit to TS is simply the IDE integration.  Without it, any other static type checker superset of JavaScript is an also-ran.

pretty close to a non-starter on windows.

I've been using the new MS Terminal application with WSL2 a lot the past couple months for work and usually script a lot via node/npm scripts and don't rely on too many libraries, mostly yargs, inquirer and chalk.

May consider colorette and others.

1. https://www.npmjs.com/package/yargs
2. https://www.npmjs.com/package/inquirer
3. https://www.npmjs.com/package/chalk

Interesting... I've used chalk a couple times, not sure if this is much/any better though.  Following the rgb/hex/24-bit color support with some interest.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/flatMap

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/flat

While I appreciate the effort, I'm not sure it's quite so cut and dry.

One of the biggest problems that I often encounter isn't so much what Axe, Lighthouse and WAVE show is actually being able to navigate your site with a keyboard alone.  Visually impaired people generally don't use a mouse for browsing... not being able to have proper navigation is huge.

There are only a handful of roles and/or aria-* attributes that all web developers working on public facing applications should know about.

Should put links to the respective icon sites in the show notes after the summary.

Also, may want to reference the extended Material Design Icons library over the one from google, there are several target publications of this library, including one mdi-material-ui package for the material-ui react components.

https://materialdesignicons.com/

Generally you should only concern yourself with the document.documentElement.clientWidth/clientHeight... as you really don't have any control over much else.

You may want to use the window.innerWidth/innerHeight if you intend to override scrolling behavior, setting html overflow to hidden, and your own scrolling regions.

The use of other information is mostly going to only help you in terms of knowing what *could* be used for full-screen interaction (F11 mode) if you're doing gaming/simulation work.