pnpm-v10-to-v11 does not work on Windows
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 16
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Running pnpm-v10-to-v11 does not produce any changes on Windows, it silently completes with no files modified.
npx codemod run pnpm-v10-to-v11
[1/2] 🔍 Resolving package from registry: https://app.codemod.com ...
[2/2] 🏁 Running codemod: pnpm-v10-to-v11
Workflow started c9db3f81-acab-4e38-8445-d3c696abb758
⏺ Run pnpm v10 → v11 migration
⚠ Shell command requires approval
Step: Run pnpm v10 → v11 migration
Node: Migrate to pnpm v11
Command:
node -e "import(require('url').pathToFileURL(process.env.CODEMOD_PATH+'/dist/index.js').href)"
> Run this command? Yes
Workflow completed in 3.0s
Run summary
Modified 0
Unmodified 0
Running the same command in WSL does migration correctly.
On Windows there is no "pnpm v11 migration complete" message.
On both platforms the Modified/Unmodified counters are zero.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with npx codemod run pnpm-v10-to-v11 on Windows and compare it with WSL. Start from the migration entry point shown in dist/index.js, then trace why the Windows run reports zero changes and omits the completion message. Done means the Windows command performs the migration and reports completion with appropriate counters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100