Update dependency immer to v11

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
immer	^9.0.21 → ^11.0.0

---

Release Notes

immerjs/immer (immer)

v11.1.4

Compare Source

Bug Fixes

• handle nested proxies after spreading and inserting into an array (90a7765)

v11.1.3

Compare Source

Bug Fixes

• recursive T for WritableDraft (#​1197) (78ea694)

v11.1.2

Compare Source

Bug Fixes

• bogus commit to retest release (c329ddb)

v11.1.0

Compare Source

This feature release adds a new optional "array method overrides" plugin that significantly speeds up array methods when accessing drafts.

Changelog

Performance Improvements

As part of the recent performance optimization work, our benchmarks showed that all Proxy-based immutable update libraries were drastically slower than vanilla JS when calling both mutating and non-mutating array methods. After investigation, it turns out that an array method like arr.filter() causes the Proxy's get trap to trigger for every single item in the array. This in turn forces creation of a new Proxy and internal Immer metadata for every item, even though this was just a read operation and no items were being updated.

This release adds a new enableArrayMethods plugin that will override draft array methods to bypass the draft and directly operate on the underlying wrapped array instance. This significantly speeds up array operations.

When enabled, the plugin overrides these array methods:

• Mutating: push, pop, shift, unshift, splice, reverse, sort
• Non-mutating: filter, slice, concat, flat, find, findIndex, findLast, findLastIndex, some, every, indexOf, lastIndexOf, includes, join, toString, toLocaleString

Our benchmarks show that the overridden methods (plus the other perf changes in Immer 10.2 and 11.0) are 50-80% faster than the baseline behavior of Immer 10.1.

The plugin adds about 1.5-2K minified to Immer's bundle size.

It's important to note that the plugin does change the "safe to mutate a draft" semantics of Immer. Any of these methods that receives an array item as a callback argument will not automatically wrap that item in a Proxy!. That means that if you try to mutate an argument in a method such as filter, it will actually mutate the real underlying object, which will cause bugs in your app. This is an intentional design tradeoff. Semantically, all of these methods imply read-only access to array values, so if your code tries to mutate an array item in a callback, that is a bug in your code.

Note that this does not override map, flatMap, forEach, or reduce / reduceRight. Those methods do imply either side effects and potential mutations, or returning arbitrary values. Given that, we determined it was both safest and simplest to keep their behavior as-is.

See the Array Methods Plugin docs page for further details on the behavior of the overridden methods.

What's Changed

• Override array methods to avoid proxy creation while iterating and updating by @​markerikson in #​1184

v11.0.1

Compare Source

Bug Fixes

• (dummy fix to release freeze fix per #​1193) (99e59a8)

v11.0.0

Compare Source

Performance Improvements

• Rewrite finalization system to use a callback approach instead of tree traversal (#​1183) (d6c1202)

BREAKING CHANGES

• enable loose iteration by default

• Simplify some iteration checks

• Allow passing type to get/set utils to skip archetype lookup

• Convert assigned_ to Map

• Enable loose iteration

• Replace recursive tree finalization with targeted callbacks

Ported Mutative's "finalization callback" approach as a more targeted and performant implementation for finalization compared to the existing recursive tree traversal approach:

• Added cleanup callbacks for each draft that's created
• Added callbacks to handle root drafts, assigned values, and recursing
  inside of plain values
• Updated state creation to return [draft, state] to avoid a lookup
• Rewrote patch generation system to work with callbacks instead of
  during tree traversal

• Update self-reference test with new behavior
• Apply code review suggestions
• Byte-shave scopes and patch plugin usage
• Inline finalizeAssigned
• Move fixPotentialSetContents to plugin
• Byte-shave typeof utils
• Byte-shave Object references
• Byte-shave field names and arrow functions

v10.2.0

Compare Source

Features

• Optimize Immer performance where possible, introduce setUseStrictIteration (#​1164) (e1996ce)

v10.1.3

Compare Source

Bug Fixes

• Mark exports as pure, for better tree-shakability (#​1124) (85faaa2)

v10.1.2

Compare Source

Bug Fixes

• non-enumerable (immutable) methods on Map/Set (#​1069) (aa24400)
• Update package.json exports for react-native (#​1159) (b2fcc66)

v10.1.1

Compare Source

Bug Fixes

• export lost types (#​1116) (5a8f6e7)
• Make applyPatches to accept readonly Patch[] (#​1094) (4da2e0d)

v10.1.0

Compare Source

Features

• performance: Make non-strict mode faster for classes. Addresses #​1071 (53e3203). Immer 10.x solved slow iteration for plain JS objects. This update applies the same handling to class instances. In cases this makes class instance handling 3 times faster. Note that this slightly modifies the behavior of Immer with classes in obscure corner cases, in ways that match current documentation, but do not match previous behavior. If you run into issues with this release icmw. class instances, use setUseStrictShallowCopy("class_only") to revert to the old behavior. For more details see https://immerjs.github.io/immer/complex-objects#semantics-in-detail

v10.0.4

Compare Source

Bug Fixes

• Fix handling of Symbol and non-enumerable properties in finalization / freeze. Fixes #​1096, #​1087, #​1091 (#​1105)) (8949a3e)

v10.0.3

Compare Source

Bug Fixes

• don't use .mjs file for react-native, which isn't supported by default. Fixes #​1058 #​1065 (#​1075) (f6736a4)

v10.0.2

Compare Source

Bug Fixes

• export Objectish type (#​1043) (75e004d)
• Move index.js.flow from dist/ -> dist/cjs/ to match index.js (#​1038) (a3b5603)

v10.0.1

Compare Source

Bug Fixes

• production bundle was loaded incorrectly, fixes #​1037 (707e72b)

v10.0.0

Compare Source

Release notes

• [breaking change] Immer 10 only supports modern browsers, that have support for Proxy, Reflect, Symbol and Map and Set.
• [breaking change] There is no longer a UMD build exposed (thanks Mark Erikson for modernizing the build setup in #​1032!
• [breaking change] getters and setters are ignored by default on plain object, as this is a very uncommon case and provides a significant performance boost (ca 33%, but depends a lot on the scenario). Fixes #​867, #​1012. Thanks hrsh7th for implementing it in #​941!
• [breaking change] Promise based reducers are no longer supported. Conceptually it is an anti pattern to hold on to drafts over time. If needed the old behavior can still be achieved by leveraging createDraft and finishDraft.
• [breaking change] ES5 mode (for legacy browsers) has been dropped. If your project relies on enableES5(), you SHOULD NOT upgrade Immer. enableES5 has been removed.
• [breaking change] produce is no longer exposed as the default export. This improves eco system compatibility, and makes sure that there is only one correct way of doing things
• [breaking change] enableAllPlugins has been removed, use enablePatches(); enableMapSet() instead
• [breaking change] shortening the length of a JSON array now results in delete patches, rather than a mutation of the length property, in accordance with JSON spec. Thanks kshramt for implementing this in #​964!
• Immer is now an ESM package that can be directly imported into the browser. CJS should still work, UMD support has been removed.

Overall, there is a rough performance increase of 33% for Immer (and in some cases significantly higher), and the (non gzipped) bundle size has reduced from 16 to 11.5 KB, while the the minimal gzipped import of just produce has remained roughly the same at 3.3 KB.

For more details, see #​1015

Migration steps

1. If you have any enableES5() call, don't migrate
2. When using getters/ setters icmw plain objects, call useStrictShallowCopy(true) at startup
3. Replace all default imports: Replace import produce from "immer" with import {produce} from "immer"
4. Replace all calls to enableAllPlugins() with enablePatches(); enableMapSet(); to be more specific and smoothen future migrations.
5. If any producer returned a Promise, refactor it to leverage createDraft instead. Roughly:

const newState = await produce(oldState, recipe)

// becomes
const draft  = createDraft(oldState)
await recipe(draft)
const newState = finishDraft(draft)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coveralls]

Coverage Report for CI Build 24257530993

Coverage remained the same at 40.886%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	13769
Covered Lines:	6073
Line Coverage:	44.11%
Relevant Branches:	6991
Covered Branches:	2415
Branch Coverage:	34.54%
Branches in Coverage %:	Yes
Coverage Strength:	28.97 hits per line

---

💛 - Coveralls

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 11.x releases. But if you manually upgrade to 11.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.