pnpm
“Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces, or managing dependencies with catalogs, patches, or overrides.”
references
aipkg.jsonGENERATION.mdLICENSE.txtREADME.mdreferences/best-practices-ci.mdreferences/best-practices-migration.mdreferences/best-practices-performance.mdreferences/core-cli.mdreferences/core-config.mdreferences/core-store.mdreferences/core-workspaces.mdreferences/features-aliases.mdreferences/features-catalogs.mdreferences/features-hooks.mdreferences/features-overrides.mdreferences/features-patches.mdreferences/features-peer-deps.mdSKILL.md- 01SQP-270%HIGH
references/best-practices-migration.md:16
detailhide
The migration guide instructs users to run `rm -rf node_modules package-lock.json` without any warning about data loss or confirmation prompts. While these are generated files that should be safe to delete, the command is presented in a context where users following migration guidance might accidentally run it with incorrect paths or permissions, potentially deleting unintended directories. The lack of any cautionary language increases risk.
14```bash15# Remove npm lockfile and node_modules16rm -rf node_modules package-lock.json1718# Install with pnpmfix Add a warning box or note before destructive commands. Include explicit instructions like 'Verify you are in the project root directory' or suggest safer alternatives such as using `pnpm install --force` which handles cleanup automatically without requiring manual deletion commands.