chore: align remaining dev deps and tooling config with core

[cryptodev-2s]

Top of stack #315, on #317.

Dep	From	To
typedoc	^0.23.15	^0.25.13
@lavamoat/preinstall-always-fail	^1.0.0	^2.1.0
jest-when	^3.6.0	^3.7.0

The typedoc bump fixes a live break. typedoc 0.23 caps at TypeScript 5.0, so once #311 moved us to ~5.3.3, yarn build:docs crashed with Cannot read properties of undefined (reading 'name'). Nothing caught it because PR CI never runs build:docs, only the docs publish workflow does.

Also .nvmrc v18 to lts/*, and @ts-bridge/* added to npmPreapprovedPackages. Both match core.

Left alone on purpose:

• depcheck is not swapped for knip. Core's knip config is 292 lines of monorepo specific tuning, and PR#8 of the migration guide strips knip.config.* from the package anyway.
• oxfmt stays at ^0.44.0 even though @metamask/auto-changelog@6.2.1 peer requests ^0.45.0. Core pins the same pair, so bumping would diverge from it.

---

Note

Low Risk
Tooling-only changes (Node version hint, Yarn allowlist, devDependencies); no runtime library or security-sensitive application logic is modified.

Overview
Aligns Node and Yarn policy with MetaMask core and bumps a few dev dependencies so docs and installs stay healthy after the TypeScript 5.3 upgrade.

.nvmrc now tracks lts/* instead of pinning v18. .yarnrc.yml adds @ts-bridge/* to npmPreapprovedPackages, so those packages can bypass the 3-day npm age gate (same as core).

Dev dependency bumps: typedoc ^0.23.15 → ^0.25.13 (restores yarn build:docs with typescript ~5.3.3; 0.23 only supported TS through 5.0 and was failing at doc generation), @lavamoat/preinstall-always-fail ^1.0.0 → ^2.1.0, and jest-when ^3.6.0 → ^3.7.0, with matching yarn.lock updates for transitive deps (e.g. marked, minimatch, shiki).

^{Reviewed by Cursor Bugbot for commit 6f36a6c. Bugbot is set up for automated code reviews on this repo. Configure 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
	@​lavamoat/​preinstall-always-fail@​1.0.0 ⏵ 2.1.1			+5
	jest-when@​3.6.0 ⏵ 3.7.0	+1		+1
	typedoc@​0.23.28 ⏵ 0.25.13	+2		-2

View full report

[socket-security]

Caution

MetaMask internal reviewing guidelines:

• Do not ignore-all
• Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
• Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
  @SocketSecurity ignore npm/PACKAGE@VERSION

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Obfuscated code: npm shiki is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package.json → npm/typedoc@0.25.13 → npm/shiki@0.14.7 ℹ 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 support@socket.dev. 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/shiki@0.14.7. 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.
Warn		Install-time scripts: npm @lavamoat/preinstall-always-fail during preinstall Install script: preinstall Source: echo "Don't run npm lifecycle scripts by default! Create a .yarnrc or .npmrc and set enableScripts: false. Then, whitelist them with @lavamoat/allow-scripts" && exit 1 From: package.json → npm/@lavamoat/preinstall-always-fail@2.1.1 ℹ Read more on: This package | This alert | What is an install script? 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 support@socket.dev. Suggestion: Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@lavamoat/preinstall-always-fail@2.1.1. 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