chore: bump root lint and formatting devDependencies

[jeremytsng]

Explanation

Bumps the root lint/format devDependencies to current ranges: eslint-plugin-import-x, eslint-plugin-jest, eslint-plugin-jsdoc, eslint-plugin-n, eslint-plugin-prettier, eslint-plugin-promise, prettier. Root-only tooling; no package code changes.

Two required follow-ons included:

• eslint-plugin-n ≥17.24 flags import.meta.dirname as unsupported under engines.node: >=20 (needs Node ≥20.11). Replaced with dirname(fileURLToPath(import.meta.url)) in eslint.config.mjs. This was latent on main — any lockfile refresh would have broken yarn lint.
• New eslint-plugin-import-x pulls unrs-resolver; added to the LavaMoat allow-scripts denylist.

eslint-import-resolver-typescript intentionally stays at ^3.6.3 — 4.x violates the peer range of @metamask/eslint-config-typescript@15. @lavamoat/allow-scripts is left untouched.

Verified: yarn lint, yarn build, yarn test all green.

References

N/A

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	eslint-plugin-promise@​7.2.1 ⏵ 7.3.0	+1
	eslint-plugin-import-x@​4.6.1 ⏵ 4.17.1	+1		+1	-2
	eslint-plugin-prettier@​5.2.1 ⏵ 5.5.6	+1			-1
	eslint-plugin-n@​17.15.1 ⏵ 17.24.0				-2
	eslint-plugin-jsdoc@​50.6.1 ⏵ 50.8.0	+1			+1
	prettier@​3.4.2 ⏵ 3.9.6	+14		+1
	eslint-plugin-jest@​28.10.0 ⏵ 28.14.0	+1		+1	+3

View full report

[socket-security]

Warning

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)
Warn		Potential code anomaly (AI signal): npm eslint-plugin-import-x is 65.0% likely to have a medium risk anomaly Notes: No obvious malware behavior (no network, filesystem, or credential access) is present in this snippet. However, the rule performs dynamic evaluation using node:vm on attacker-controlled text taken directly from the source file’s leading comments. In a supply-chain/tooling context (e.g., linting untrusted code), this creates a meaningful toolchain execution risk even though the intention is validation. Primary risk is execution/side effects during linting, not runtime compromise of the shipped package. Confidence: 0.65 Severity: 0.52 From: package.json → npm/eslint-plugin-import-x@4.17.1 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/eslint-plugin-import-x@4.17.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.
Warn		Potential code anomaly (AI signal): npm prettier is 60.0% likely to have a medium risk anomaly Notes: No direct evidence of embedded malware (no eval/new Function, no credential theft, no obvious backdoor/persistence, no explicit network exfiltration) is visible in this fragment. The dominant security concern is supply-chain/execution risk: the code dynamically imports and executes formatter plugins based on user/config-supplied plugin identifiers and resolution rooted at process.cwd(). Additionally, it can read/write local files (including writing formatted output back to caller-specified paths) and uses predictable temp JSON files that may be susceptible to interference in shared environments. Security posture depends heavily on whether plugin inputs and file paths are trusted/validated and whether dependency/plugin resolution is constrained. Confidence: 0.60 Severity: 0.55 From: package.json → npm/prettier@3.9.6 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/prettier@3.9.6. 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