lirantal / lirantal/create-node-lib
Bug: When choosing pnpm as package manager still the npmrc config is copied of
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 45
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
## Expected Behavior
Only the pnpm config file should be copied over, not the npmrc file
## Current Behavior
When choosing pnpm as package manager still the npmrc config is copied of
## Possible Solution
## Steps to Reproduce (for bugs)
1.
2.
3.
4.
## Context
## Your Environment
- Library Version used:
- Node.js version (e.g. Node.js 5.4):
- Operating System and version (desktop or mobile):
Contributor guide
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
Start by reproducing project scaffolding with pnpm selected and inspect which package-manager configuration files are copied into the generated project. Trace the package-manager selection path to find why the npmrc file is included, then verify that only the pnpm configuration is copied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100