Update dependency np to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
np	10.0.0 -> 10.2.0

---

Release Notes

sindresorhus/np (np)

v10.2.0

Compare Source

• Support bun.lock lock file (#​761) 8187dfe
• Update dependencies a45f816

---

v10.1.0

Compare Source

• Add support for Bun (#​756) cbc6f3b
• Update dependencies 8fdac0c

v10.0.7

Compare Source

• Allow publishConfig.registry to be npm default registry when using Yarn berry (#​750) 6c5eee3

v10.0.6

Compare Source

• Fix usage with pnpm and --any-branch or --branch (#​745) d0c1493

v10.0.5

Compare Source

• Fix npm 10 compatibility for real (#​744) 34409be

v10.0.4

Compare Source

• Fix compatibility with npm 10 (#​743) 4caa295

v10.0.3

Compare Source

• Fix publish OTP for Yarn Berry (#​741) 02f60c7

v10.0.2

Compare Source

• Use npm for tagging versions when pnpm is the chosen package manager (#​739) 770418f

v10.0.1

Compare Source

• Fix compatibility with npm 10 (#​737) 9fdebd5

v10.0.0

Compare Source

Breaking

• Remove the --yarn flag (#​730) 4b3b599
  • The functionality is replaced by --package-manager. See below.

Improvements

• Add --package-manager flag (#​730) 4b3b599
  • This acts like the packageManager field in package.json. np will default to reading package.json, and look for lockfiles to determine the best package manager as a last resort.
• Add pnpm support (#​730) 4b3b599

v9.2.0

Compare Source

• Fix yarn npm publish for scoped packages 8d3a984
• Fix broken revert code after publish failure 819ed29

v9.1.0

Compare Source

• Add Yarn Berry support (#​723) 0d9522b

v9.0.0

Compare Source

Breaking

• Require Node.js 18 and npm 9 6c2e00e

Improvements

• Group unpublished files in folders (#​716) c31c2bc
• improve messages related to new files and dependencies (#​702) ad7b09e

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

♻ 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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"9.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/parser
npm ERR!   dev @typescript-eslint/parser@"7.5.0" from the root project
npm ERR!   peer @typescript-eslint/parser@"^7.0.0" from @typescript-eslint/[email protected]
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     dev @typescript-eslint/eslint-plugin@"7.5.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-22T07_09_38_355Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-22T07_09_38_355Z-debug-0.log

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"9.21.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8" from [email protected]
npm error node_modules/eslint-plugin-import
npm error   dev eslint-plugin-import@"2.29.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-03-06T06_30_53_936Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-03-06T06_30_53_936Z-debug-0.log