fix(deps): Update dependency @xstate/react to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@xstate/react (source)	^1.2.0 -> ^2.0.1

---

Release Notes

statelyai/xstate (@​xstate/react)

v2.0.1

Compare Source

Patch Changes

• #​3089 862697e29 Thanks @​Andarist! - Fixed compatibility with Skypack by exporting some shared utilities from root entry of XState and consuming them directly in other packages (this avoids accessing those things using deep imports and thus it avoids creating those compatibility problems).

v2.0.0

Compare Source

Major Changes

• #​2674 e5a8b8dff Thanks @​Andarist, @​mattpocock! - To avoid breaking any consumers and to leverage the newly introduced typegen support, the major version of this package had to be bumped. While you can still use it with older versions of TS, the typegen support in this package requires TS version 4.0 or greater.

  When using hooks from @xstate/react it's recommended to skip providing explicit generics to them. Note that that generics list has changed since v1 and we now only accept a single generic, TMachine.

• #​2674 ab919d300 Thanks @​Andarist! - Removed already deprecated useService from @xstate/react. You can replace its usage with useActor.

Patch Changes

• #​2957 8550ddda7 Thanks @​davidkpiano! - The repository links have been updated from github.com/davidkpiano to github.com/statelyai.

---

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate using a curated preset maintained by . View repository job log here

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	shell-quote@​1.7.2
	number-is-nan@​1.0.1
	side-channel@​1.0.4
	sort-order@​1.0.1
	util.promisify@​1.0.1
	tty-browserify@​0.0.0 ⏵ 0.0.1
	safer-buffer@​2.1.2
	object.hasown@​1.1.0
	object.fromentries@​2.0.5
	path-parse@​1.0.7
	object-keys@​1.1.1
	object-is@​1.1.5
	object.getownpropertydescriptors@​2.1.3
	unbox-primitive@​1.0.1
	object.values@​1.1.5
	string.prototype.matchall@​4.0.6
	string.prototype.trimend@​1.0.4
	string.prototype.trimstart@​1.0.4
	which-boxed-primitive@​1.0.2
	regexp.prototype.flags@​1.3.1
See 313 more rows in the dashboard

View full report

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-spring-bottom-sheet	❌ Failed (Inspect)			May 14, 2025 10:33am

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Warn		[email protected] has a Critical CVE. CVE: GHSA-g4rg-993r-mgx7 Improper Neutralization of Special Elements used in a Command in Shell-quote (CRITICAL) Affected versions: <= 1.7.2 Patched version: 1.7.3 From: package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report