Remove explicit npm version from package.json

[joshblack]

Remove the explicit npm cli version that we have in our root package.json. This was to prevent npm@11 being downloaded which was causing flakiness in our CI suite 😅

Hopefully with the recent releases of npm@11 this issue has gone away. If not, we can revert this change.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f19d1bf

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

[github-actions]

size-limit report 📦

Path	Size
packages/react/dist/browser.esm.js	94.49 KB (0%)
packages/react/dist/browser.umd.js	94.6 KB (0%)

[Copilot]

Pull Request Overview

This PR removes the explicit npm CLI version (“packageManager”) from the root package.json to avoid CI flakiness caused by npm@11 downloading.
Key changes:

• Deleted the pinned packageManager field from package.json

Comments suppressed due to low confidence (1)

package.json:110

• [nitpick] Consider updating related contributor or setup documentation (e.g., README or CONTRIBUTING.md) to note that npm is no longer pinned in package.json, so developers know which npm versions are supported/recommended.

"packageManager": "[email protected]+sha512.8ab88f10f224a0c614cb717a7f7c30499014f77134120e9c1f0211ea3cf3397592cbe483feb38e0c4b3be1c54e347292c76a1b5edb94a3289d5448484ab8ac81"