Conversation
- Bump immer from ^9.0.21 to ^11.1.4 - Drop useProxies option in src/lib.js — immer v10 dropped ES5 mode and Proxy is now the only supported backend - Remove easy-peasy/proxy-polyfill subpath export — enableES5() no longer exists in immer - Document the subpath removal as a v7 breaking change in the upgrade guide - Keep easy-peasy/map-set-support — enableMapSet() is still opt-in in v11 Closes #1034 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The proxy-polyfill subpath documented here was removed in #1035 — immer v10 dropped ES5 mode entirely, so the IE11 / non-Proxy environment workflow described on this page no longer applies. - Drop the "Polyfilling Proxy" and "Create React App IE11 Support" sections. - Reframe the page around React 19's supported runtimes (all ship native Proxy). - Keep the "Why Immer?" overview and the Map/Set support section. - Add a v6 → v7 migration callout pointing at the upgrade guide for consumers who imported the removed subpath. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Upgrades the
immerdependency from^9.0.21to^11.1.4. Closes #1034.Changes
package.json— bumpimmerto^11.1.4; remove./proxy-polyfillfromexportsandfiles.src/lib.js— drop theuseProxiesconstructor option from our customImmerinstance. immer v10 dropped ES5 mode entirely, souseProxiesno longer exists andProxyis the only supported backend. KeptautoFreeze: false(still required for the mixed mutability/immutability pattern around computed properties).proxy-polyfill.js+proxy-polyfill.d.ts— deleted. The shim calledimmer.enableES5(), which was removed in immer v10. Every browser supported by React 19 has nativeProxy, so no replacement is needed.website/docs/docs/upgrading-from-v6/README.md— documents the subpath removal as a v7 breaking change.What stayed the same
easy-peasy/map-set-supportsubpath — verified empirically thatenableMapSet()is still a real opt-in in immer v11 (Map/Set draft support throws without it). Kept as-is.isDraft,current,original,produce,setAutoFreeze) is unchanged in v11.Verification
yarn test— 193 passed (incl.computed,persist,immer,migrations)yarn test:coverage— 193 passed under v8 instrumentation; 96.49% statementsyarn dtslint— cleanyarn build— clean (Rollup ESM + CJS for index + server)yarn lint— only one pre-existing warning, unrelated to this change🤖 Generated with Claude Code