Update dependency immer to v11

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
immer	^10.1.1 → ^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

---

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.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.