chore(deps): update dependency np to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
np	^9.0.0 → ^10.0.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

---

Configuration

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

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

♻ Rebasing: Whenever PR is behind base branch, 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.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	np@​9.2.0 ⏵ 10.2.0	+1		+1

View full report

[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 "▶" to expand/collapse)
Warn		Obfuscated code: npm safer-buffer is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: package-lock.json → npm/@wdio/[email protected] → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. 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