chore: migrate from npm to pnpm - #59
Conversation
Removes package-lock.json in favor of pnpm-lock.yaml and pins the package manager via the packageManager field. pnpm hard-links dependencies from a shared global store, deduplicating them across repos to save local disk. Build (tsc + esbuild) verified green under pnpm. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 920a8c3f4b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "description": "A zero-terminal, real-time sync engine powered by your own Cloudflare Worker.", | ||
| "main": "main.js", | ||
| "type": "module", | ||
| "packageManager": "pnpm@9.15.0", |
There was a problem hiding this comment.
This migration removes the root npm lockfile, but the root CI and release workflows still install the root project with npm ci (.github/workflows/ci.yml:20 and .github/workflows/release.yml:22). I confirmed the CLI behavior with npm ci --dry-run, which exits with EUSAGE and says npm ci can only install with an existing package-lock.json or npm-shrinkwrap.json, so every push/PR and tagged release will fail before reaching the build unless these workflow steps are switched to pnpm/corepack.
Useful? React with 👍 / 👎.
1 participant
Summary
package-lock.jsonin favor ofpnpm-lock.yamland pins the package manager via thepackageManagerfield.Test plan