Enforce Yarn-Only Policy & Auto-Cleanup Forbidden Lock Files #1202
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR enforces the use of Yarn as the only package manager for this project and introduces automated cleanup for forbidden lock files and node_modules if npm or pnpm is used.
✨ What’s Changed
scripts/ensure-yarn.js
:Checks the package manager during install. If npm or pnpm is detected, it runs
scripts/clean-forbidden.sh
to removepackage-lock.json
,pnpm-lock.yaml
, andnode_modules
from both the root andexample/
directories, then exits with an error. Also it safely deletes forbidden lock files and node_modules, ignoring errors if files do not exist.preinstall
script inpackage.json
to invokeensure-yarn.js
, ensuring this check runs automatically on every install.🛡️ Why
🧑💻 Impact
🧹 No more rogue lock files! Only Yarn is allowed.