Andrew
Andrew
Bump: This is still an issue as of Electron v22.0.0.
Yep, this is still an issue. Kind of frustrating too. I spent awhile assuming I was doing something wrong. ---- Ok, so I dug around. The issue is due to...
Digging further, this line of code has used `setIn` since it was introduced: Commit Diff: https://github.com/jaredpalmer/formik/commit/123e3925a02ae952c445daef072021224ab3690a#diff-a2d99b5c519f468d81549cc342ecb0fb4096b285ee93e36a250e4fcccd963565R472 Commit File: https://github.com/jaredpalmer/formik/blob/123e3925a02ae952c445daef072021224ab3690a/src/Formik.tsx#L472 But at that time, *there was no* `stateRef`, leading me to...
Adding details to this issue: This does not happen only for CommonJS modules. I'm able to reproduce it still in NodeJS v20.11.1 when running many dynamic imports for different modules...
(TL;DR: Apparently @dnd-kit/react is way too new to use.) Even though `evt.operation.source.sortable` appears when running...  It's also not public: Even worse, I just tried inspecting `source.sortable.index` and `target.sortable.index` and...
I needed nested draggable/droppable areas. Since this is broken, I reverted back to the old `@dnd-kit/core` / `@dnd-kit/utilities` packages, re-developed my code to stop using `@dnd-kit/sortable`, and used the raw...
Still partially reproducible in v3.6.2. I also ran into this, as @jjspace did, with regular imports. The issue has nothing to do with dynamic imports. With that said, it does...
@clauderic, Please merge this. It's bugging me a lot. The bad syntax is completely screwing up the highlighting: 
If I read through this correctly, this is not an issue with Zod; it's just a Duplicate Dependency issue, which can happen with any package. Furthermore, Zod v4 *even still*...
FWIW, with some experimentation (but not with certainty), constructor ordering seems to be column-major. i.e., `mat3(vec3, vec3, vec3)` *seems* to be vectors of columns, not rows.