"Maximum call stack exceeded" with circular references about immer HOT 5 OPEN

Argh, the JS world is impossible. 50% is like "non-enumerables and proxies have very specific meanings", and the other half is like "I expect non-enumerables and symbol to work just like the rest, why treat them irregularly" 🤣

from immer.

Yeah I guess the only way to deal with this is to make all the behavior of irregular properties of any kind (enumerable x getter x proxy) all configurable. That will be a a bit bigger project though so probably more for a next major.

from immer.

Would you mind trying setting the setUseStrictShallowCopy(false) flag? Maybe in combination with version 10.0.4-beta?

from immer.

@mweststrate I get it. I apologize for contributing to your pain as an open-source maintainer.

setUseStrictShallowCopy(false) with 10.0.4 or 10.0.4-beta seems to have no effect.

For what it's worth, Immer 9.x's behavior seemed consistent and worked for my purposes:

• Preexisting symbol props are skipped by Immer, as consistent with Object.values, JSON.stringify, etc. (I.e., this issue.)
• If I add/set a symbol prop within Immer, it handles it well enough to avoid leaking proxies. (I.e., #1087.)

Hopefully that's too ad hoc / too much of a special case - but, if you decide it is, I understand.

from immer.

Another way to reproduce this is trying to modify an object that contains React context: https://codesandbox.io/p/devbox/festive-gagarin-9mkfx9

For what it’s worth, the repro seems to work using [email protected]

from immer.