Updated immer library to 11.1.3

[nZeus]

This PR updates the immer dependency so that this library can also be used with angular 21

[nZeus]

cc: @WalterNorthwoods
Could you please review the PR?

[WalterNorthwoods]

I did. Alas, when rebuilding I got a bunch of errors. But thank you for telling us about the desired version of immer. Could you please tell us why you want that version?

…

On Thu, Jan 8, 2026, 03:50 Ilia Tsvetkov ***@***.***> wrote: *nZeus* left a comment (NorthwoodsSoftware/gojs-angular#69) <#69 (comment)> cc: @WalterNorthwoods <https://github.com/WalterNorthwoods> Could you please review the PR? — Reply to this email directly, view it on GitHub <#69 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACV7Y57XJABEUVFGJ7KHJ5D4FYK6JAVCNFSM6AAAAACQ24KKV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMRSHA2DQMJVGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[nZeus]

The current version is incompatible with the angular 21

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/immer
npm error   immer@"11.1.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer immer@"^10.1.1" from [email protected]
npm error node_modules/gojs-angular
npm error   gojs-angular@"2.1.3" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/immer
npm error   peer immer@"^10.1.1" from [email protected]
npm error   node_modules/gojs-angular
npm error     gojs-angular@"2.1.3" from the root project

Ideally it's good to update the version of angular to v21, but that gives some weird errors:

So the safest option is to only update immer.

I did. Alas, when rebuilding I got a bunch of errors.

Have you tried to clean the folders first?

rm -Rf node_modules && rm package-lock.json
npm cache clean --force

[WalterNorthwoods]

Thanks for suggesting *npm cache clean*. Although it's better now, I'm still getting configuration errors. This will take time to figure out by someone more knowledgeable than I am.

…

On Thu, Jan 8, 2026 at 5:31 AM Ilia Tsvetkov ***@***.***> wrote: *nZeus* left a comment (NorthwoodsSoftware/gojs-angular#69) <#69 (comment)> The current version is incompatible with the angular 21 npm error code ERESOLVE npm error ERESOLVE could not resolve npm error npm error While resolving: ***@***.*** npm error Found: ***@***.*** npm error node_modules/immer npm error immer@"11.1.3" from the root project npm error npm error Could not resolve dependency: npm error peer immer@"^10.1.1" from ***@***.*** npm error node_modules/gojs-angular npm error gojs-angular@"2.1.3" from the root project npm error npm error Conflicting peer dependency: ***@***.*** npm error node_modules/immer npm error peer immer@"^10.1.1" from ***@***.*** npm error node_modules/gojs-angular npm error gojs-angular@"2.1.3" from the root project Ideally it's good to update the version of angular to v21, but that gives some weird errors: image.png (view on web) <https://github.com/user-attachments/assets/4826a3c5-a781-4616-bee5-d8d6402741e8> So the safest option is to only update immer. I did. Alas, when rebuilding I got a bunch of errors. Have you tried to clean the folders first? rm -Rf node_modules && rm package-lock.json npm cache clean --force — Reply to this email directly, view it on GitHub <#69 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACV7Y5ZJLSIEQ6PBGFSMP734FYWXNAVCNFSM6AAAAACQ24KKV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMRTGIZDOMBUGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[simonsarris]

We'll look at this today

[simonsarris]

Thanks for your patience Ilia. We just published [email protected], if you want to give it a try. I also removed zones as a dependency, which hopefully causes no issues.