Echo JS 0.11.0

Congrats on the release... I'd probably post it to Hacker News as it's really OT here, I know you mention RIOT.js, but the project really isn't JS centric.

Yeah, I'm in a pretty locked down env at work, and couldn't get to the article itself.

FWIW MozDev Docs - https://developer.mozilla.org/en-US/docs/Web/API/Bluetooth

Needs some work on the constraints for mouse interactions which can totally break positioning.. at least for me in Chrome.

https://rsuitejs.com/

https://github.com/rsuite/rsuite

Interesting, though definitely a large composite component.  Nice to see the MIT license, I seem to recall some SVAR bits being some GPL variant, but my quick look at the github repos seem to be MIT now across the board.

It's not expressly a TS thing, this will likely require a PR change to the linter/checker... maybe submit a request for a Frozen<T> type to be added to the core.

Aside, you can always use Object.freeze, but this can have odd side effects.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/freeze

Nice writeup... I would point out that these kinds of tests can be somewhat costly and very time consuming in terms of the time they take to run.

Depending on your workflows, you may want them earlier or later in your lifecycle.

Another point worth mentioning, is that you will want to consider device/viewport configurations as well.  I use my phone (Android) with Text Accessibility cranked to max because of visibility issues that glasses won't correct.  I cannot tell you how many times I will face a mobile dialog or other content that is completely unusable/broken for me.  The other issue is having things forced too small, though the PS's triple-tap zoom helps significantly there.

Of course the Accessibility rabbit hole is an adjacent topic beyond the minimum viewport testing.

Two books that still hold a lot of value are "High Performance Websites" and "Even Faster Websites" both by Steven Souders who works(ed) on web performance at Google.

There are a lot of tidbits like this that can add up a lot.

Personally, I tend to deploy/configure most of the applications that I work on such that all requests are to a single origin that may reverse-proxy to differing systems/applications on the backend.  For example, I almost always separate static resources, /api and /auth from each other.

Gotta love evergreen browsers... this was added as part of ES2022 and works in most browsers.  Though Safari doesn't seem to log the cause by default.  You may also need to add additional logic to output to external loggers as well.

Noce feature to have...  I'll usually add a statusCode and other properties into my HTTP handler stack in TS in order to do custom error handling for short circuit responses.