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?
With data attributes, any current browser supports the dataset property on the dom object... so e.target.dataset.id instead of e.target.getAttribute('data-id')
Other than that, the useCallback method is interresting at least.
I tend to prefer data attributes (dataset) because then it renders and is able to be utilized by ui/integration test frameworks.