Bump version of @xtate/immer package to align with updated dependencies

[lozandier]

Fixes inconsistent non-bumping of package version like other xstate packages that had the same recent updates of peer dependencies four days ago (inconsistent how packages such as @xstate/react and @xstate/svelte were handled when their peer dependencies were updated).

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 16b127d28ad5849a1547a988133b2f9c3737a266

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codesandbox-ci[bot]]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 16b127d28ad5849a1547a988133b2f9c3737a266:

Sandbox	Source
XState Example Template	Configuration
XState React Template	Configuration

[Andarist]

The packages that you have mentioned were bumped because something has changed in their source code - not because the peer dep range has been changed. I don't see a reason here why @xstate/immer would have to be bumped.

[lozandier]

@Andarist Only reason I’m bumping is because importing it as is scans/reads xstate 4 as a dependency instead of 5 in several tools/scripts that imports NPM packages in production environments—that isn’t the case with xstate.

This package as is keeps reporting xstate 4.x as its peer dependency instead of 5.x.

Bumping the version seemingly was the past to least resistance to fix that issue.

Kevin Lozandier @.*** @.***>

On Wed, Dec 27, 2023 at 3:30 PM Mateusz Burzyński @.***> wrote:

The packages that you have mentioned were bumped because something has changed in their source code - not because the peer dep range has been changed. I don't see a reason here why @xstate/immer would have to be bumped.

— Reply to this email directly, view it on GitHub https://github.com/statelyai/xstate/pull/4639#issuecomment-1870690508, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJKUOAILKDVDAXZSPRDC2TYLSVP7AVCNFSM6AAAAABBEZWPYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZQGY4TANJQHA . You are receiving this because you authored the thread.Message ID: @.***>

[davidkpiano]

Closing this as it is now recommended to use immer directly with XState (if desired) instead of with @xstate/immer: https://stately.ai/docs/immer