Bug Description
DEVELOPMENT.md instructs new contributors to run npm install in the setup steps,
but this project exclusively uses pnpm as its package manager
("packageManager": "pnpm@9.0.0" in package.json).
CONTRIBUTING.md correctly states pnpm is required (line 61: "pnpm: Version 9 or higher is required")
and even warns "do not commit package-lock.json changes".
Running npm install will generate a package-lock.json which should not exist in this repo,
and may cause dependency resolution issues since the project uses pnpm-lock.yaml.
Steps to Reproduce
- Open
DEVELOPMENT.md → Section "1. Clone and install"
- See:
npm install (incorrect)
- Open
CONTRIBUTING.md → See pnpm is required
Expected Behavior
DEVELOPMENT.md should instruct users to run pnpm install.
Proposed Fix
# Section 1. Clone and install in DEVELOPMENT.md
git clone https://github.com/Priyanshu-byte-coder/devtrack.git
cd devtrack
pnpm install # ← change from npm install
Bug Description
DEVELOPMENT.mdinstructs new contributors to runnpm installin the setup steps,but this project exclusively uses
pnpmas its package manager(
"packageManager": "pnpm@9.0.0"inpackage.json).CONTRIBUTING.mdcorrectly states pnpm is required (line 61: "pnpm: Version 9 or higher is required")and even warns "do not commit package-lock.json changes".
Running
npm installwill generate apackage-lock.jsonwhich should not exist in this repo,and may cause dependency resolution issues since the project uses
pnpm-lock.yaml.Steps to Reproduce
DEVELOPMENT.md→ Section "1. Clone and install"npm install(incorrect)CONTRIBUTING.md→ See pnpm is requiredExpected Behavior
DEVELOPMENT.mdshould instruct users to runpnpm install.Proposed Fix