Matthew Runyon

Any updates on this? This could be adding to slow behavior in dependent packages like MUI https://github.com/mui-org/material-ui/issues/19113

Null is currently an allowed initial state (results in undefined for internal value), but not state after initial render These issues are also TS errors, so it is partially a...

Tested on React 18 (but not with any explicit concurrent features as I haven't used them before). With `useLayoutEffect` the same bug appears (in 17 and 18). I'll just make...

Implementing with state you will have to recreate most functions each render because any time the values change, any function which uses the values would change. Nearly every function uses...

I am using this which seems to play nice w/ both types. I use this constructor instead of `CustomEvent` when emitting events. If I use strict mode, I also get...

We are running Sass using the CLI included with the NPM package

I tried the latest standalone (1.37.5) release on GitHub (download and add to path) and am still getting 13k file watchers with 22 scss files in src and 146 in...

Any reason conditional exports wouldn't work for Node usage without breaking existing? https://nodejs.org/api/packages.html#packages_conditional_exports Recently ran into an issue where a package I'm consuming in Node as ESM imports redux which...

+1. This completely breaks Vite's env setup since Vite doesn't override existing env variables. So nx loads the default `.env` and then when Vite goes to load the mode specific...

Another option I could think of is nx only loading `NX_` env variables. It seems to be loading all which is causing the conflict w/ Vite. I think the current...