Move engine-strict from .npmrc to pnpm-workspace.yaml

[mm-jpoole]

pnpm 11 reads only auth and registry settings from .npmrc. Every other setting must live in pnpm-workspace.yaml or the global config, so engine-strict=true has been silently inactive since the pnpm 11 upgrade.

Confirmed in this checkout with pnpm 11.13.0: pnpm config get engine-strict returned undefined while .npmrc still set it. After the change, pnpm config get engineStrict returns true.

This moves the setting across as engineStrict: true and drops .npmrc, which held nothing else — no registry or auth line. (mm_website keeps its .npmrc for the Artifactory registry= line; this repo has no such line.)

Impact of the dead setting was small: pnpm enforces this project's own engines field either way, and engineStrict only ever applied the node key to dependencies.

Scope note: ignoreScripts and minimumReleaseAge are deliberately not added here. They were never in this repo's .npmrc and belong with the mm_website part of the ticket.

Verification

• pnpm config get engineStrict — true (was undefined)
• pnpm install --frozen-lockfile — clean, pnpm-lock.yaml unchanged
• pnpm run lint — passes
• precious lint --all — passes

Part of SCO-9212.

🤖 Generated with Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Team

Run ID: afef1e1d-4502-456b-bb3a-09abbcad02c8

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}