Kind of cool to see this... Definitely useful for something like an editor/forms environment for near state. Probably a bit harder to integrate with something like page navigation actions, especially with route changes... though can probably track/attach the state/step with route changes for better undo/back and forward tracking.
Yeah... I'd like to get them on the submission page as well... also likely with a captcha as part of submissions to slow/stop the bots.
I don't generally have time to mess with the app codebase here, mostly just act as a moderator.
Yeah... I don't see an exception in the LICENSE.txt but it's mentioned in the README. Looks like they want to restrict commercial apps to only the commercial licensing.
One that gets me is when I want to add sanity checks into a TS library function. In reality, the library may be called from straight JS, so I want to check some things to handle edge cases in a reasonable way, but often TS's type checking itself gets in the way.
Very cool, starred. I did add an "issue" suggesting that you publish a docker image to make this easier to run without worrying about direct dependencies.
Nioe writeup on these non-mutating methods. It is worth noting that if you have *VERY* large arrays in React you may want to combine with a viewport handler so only the visible nodes are rendered in order to improve DOM performance. It's one of the few places that I will lean towards earlier than later optimization as it can get noticeable fairly quickly.