Would *REALLY* prefer to see an actual instruction writeup of the content in addition to, or even instead of the Video. When looking for answers for stuff like this, you don't always want to sit for a video for something that could be mostly copy-paste from an actual article.
Nice: It's worth noting that if you don't push to your repo regularly, it will stop running the cron jobs after a while, iirc 90 days. So it's not the most reliable thing for inactive builds.
NOTE: this will emphatically not work as expected when dealing with unicode or surrogate modifiers. Realistically if you're using anything other than US-ASCII, tread carefully.
TLDR; add TypeScript type annotations support directly to JS.
It might be a good idea, would also support a pragma statement near the top of a file to support JSX transforms in the box as a standard.
WARNING: GPLv3, can be argued that any application using this library must also be GPLv3, if you're serving this library on the internet, your entire application must provide source on request.
I tend to use the following library (MIT License): https://www.npmjs.com/package/mui-icons
Which wraps svg icons in a consistent way, compatible with the mui frameworks. Provides access to several icon libraries including an expanded set of material icons (cmdi).
Nice to see this done by hand. I do generally just defer to date-fns when I need to manipulate date-time logic though. Just depends on what you're doing.
I try to keep most app slices under 200kb for JS assets. With a shared library slices between 200k-500k.
For the most part I remove articles/projects tethered to commercial products. While it relies on a commercial piece of hardware, it's otherwise on topic and I find it interesting.
Given that I'm not aware of other products that support JS and Bluetooth, mostly curious what everyone else thinks.
Should the domain be blocked, or should I keep this site's content flowing?