For what it's worth, this could be used as a base for a polyfill, which would support pretty much everything IE11 or newer.
https://github.com/tracker1/node-uuid4/
Looks interesting. Usually remove articles referring to commercial products as a primary topic. Given that you can self-host (didn't look into license though, limited time), I'm leaving this up.
It's worth mentioning that UUIDv1 and CombGuids have a time component... MS SQL Server, for example serializes with the time component first, which optimizes indexing/sorting. SQL Server itself has a sequential guid type that can be used as a primary key that includes features of the ULID as well.
I often wish that other database servers would support this serialization/deserialization structure for UUID types. As it would be beneficial to performance.
Datepicker title should switch to a month picker, then the month picker a year spinner/picker. The pattern was first really codified in the MS Ajax Toolkit, probably the only thing I liked in that framework.
The issue is that someone will use this library, and then use it for something like a date of birth field.
Generally not a fan of "Top N" or "Best N" reviews, and that holds here as well. There's no mention of exactly how these are the top/best.
There are mentions to github/npm stats but not if they are actually the top of either. I do appreciate that the article mentions an option for bare client, react, node, nextjs and angular options. I only wish the method for selection were disclosed.
There's a lot to *really* like about Deno... I know there's a few areas that are a bit more difficult, and a lot of things in Node, with no similar libraries in sight for Deno.
That said, I've played with it a bit, and I like a lot of it. I hope that more libraries and projects become compatible with published releases.
I do think the library framework release system is a bit different and could lead to some interesting innovations. I'm not completely convinced it's that much better than npm, but it definitely feels easier.
It's not really faster for most applications... it can be nice if you're enhancing a mostly static generated site.
Really wish there was a good solution for JSX with ES Modules... you *could* either do any translation server-side, or use some worker solution(s), but it gets messy. Similar for TS.
Have done a couple proof of concept bits, but it can get sticky really quickly.