# npm treats this folder as a project of its own and would resolve it from the registry,
# past pnpm-workspace.yaml's overrides and release-age gate. engines.npm in package.json is
# no valid range, and engine-strict turns that into a refusal for every command that builds
# a dependency tree here (install, ci, update, dedupe, uninstall, link, --package-lock-only,
# --ignore-scripts, --force). npx, npm exec and npm run do not check it. pnpm ignores both.
engine-strict=true
