chore(.nvmrc): specify node version 22.x to 22

[sukvvon]

Closes #

📝 Description

Add a brief description

• Update the .nvmrc file to specify 22 instead of 22.x because nvm does not recognize 22.x as a valid version.

⛳️ Current behavior (updates)

Please describe the current behavior that you are modifying

• The .nvmrc file specifies 22.x, which is not recognized by nvm, leading to issues when switching Node.js versions.

🚀 New behavior

Please describe the behavior or changes this PR adds

• The .nvmrc file now specifies 22, ensuring compatibility with nvm and seamless version switching.

💣 Is this a breaking change (Yes/No):

No

📝 Additional Information

Before

After

• This change ensures that nvm properly detects and switches to Node.js version 22.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 21d02ae

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

[vercel]

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

Name	Status	Preview	Updated (UTC)
zag-solid	✅ Ready (Inspect)	Visit Preview	Jan 8, 2025 6:36am
zag-svelte	✅ Ready (Inspect)	Visit Preview	Jan 8, 2025 6:36am
zag-vue	✅ Ready (Inspect)	Visit Preview	Jan 8, 2025 6:36am
zag-website	✅ Ready (Inspect)	Visit Preview	Jan 8, 2025 6:36am

[vercel]

@sukvvon is attempting to deploy a commit to the Chakra UI Team on Vercel.

A member of the Team first needs to authorize it.