chore: migrate from npm to pnpm - #123
Conversation
Adopt pnpm-lock.yaml and the packageManager field, update install/CI/Docker docs, and note pnpm in AGENTS.md.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
🔴 Claude BugBot Analysis
Found 1 potential bug in this PR.
low: 1
The PR is mostly a mechanical npm-to-pnpm migration (lockfile swap, packageManager field), but it introduces a typo in README.md's install instructions ('ppnpm install' instead of 'pnpm install').
|
|
||
| ```bash | ||
| pnpm install | ||
| ppnpm install |
There was a problem hiding this comment.
🔵 LOW: Typo in install command: 'ppnpm install'
The diff changes a correct pnpm install line to ppnpm install (extra leading 'p'), which is not a valid command. A user following the README setup instructions verbatim will get a 'command not found' error. Fix: change ppnpm install back to pnpm install.
Correct ppnpm→pnpm substitutions, normalize packageManager, and update GitHub Actions/Docker installs for pnpm. Co-authored-by: Cursor <cursoragent@cursor.com>
There was a problem hiding this comment.
🟢 Claude BugBot Analysis
This PR is a straightforward npm-to-pnpm migration (AGENTS.md doc/command updates, package.json packageManager field, and swapping package-lock.json for a freshly generated pnpm-lock.yaml) with no logic changes; no genuine bugs found.
No bugs were detected in this PR.
1 participant
Summary
pnpm-lock.yaml,packageManagerfield).AGENTS.md.Test plan
pnpm installpnpm run lint/ tests if present