Skip to content

fix(docs): update all npm references to pnpm#3236

Open
desireddymohithreddy0925 wants to merge 18 commits into
Priyanshu-byte-coder:mainfrom
desireddymohithreddy0925:fix/readme-pnpm-lockfile
Open

fix(docs): update all npm references to pnpm#3236
desireddymohithreddy0925 wants to merge 18 commits into
Priyanshu-byte-coder:mainfrom
desireddymohithreddy0925:fix/readme-pnpm-lockfile

Conversation

@desireddymohithreddy0925

Copy link
Copy Markdown
Contributor

Summary

Resolves inconsistencies in documentation and setup scripts by enforcing pnpm install uniformly across the repository, preventing unintended package-lock.json conflicts.

Closes #2694

Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 💥 Breaking change (fix or feature that changes existing functionality)
  • 📝 Documentation update
  • 🎨 Code style update (formatting, renaming)
  • ♻️ Refactoring (no functional changes)
  • 🧪 Testing
  • 🏗️ Build / CI/CD / Infrastructure

Description

While the README.md was recently updated to use pnpm, several other core documentation and script files still erroneously instructed users to run npm install. This often led to lockfile conflicts and failed deployments for new contributors.

Changes made:

  • DEVELOPMENT.md: Replaced all mentions of npm install and npm run with pnpm install and pnpm run.
  • CONTRIBUTING.md: Standardized all package manager commands to pnpm.
  • render.yaml: Updated the build command from npm install && npm run build to pnpm install && pnpm run build.
  • scripts/check-deps.js: Updated the printed fix message to guide developers to run pnpm install and commit pnpm-lock.yaml rather than the package-lock.json.

Note: package-lock.json is already successfully added to .gitignore from a previous PR.

DESIREDDY MOHITH REDDY and others added 18 commits June 22, 2026 18:08
…racking

# Conflicts:
#	src/components/GoalTracker.tsx
@github-actions github-actions Bot added gssoc26 GSSoC 2026 contribution type:bug GSSoC type bonus: bug fix type:docs GSSoC type bonus: documentation (+5 pts) type:testing GSSoC type bonus: tests (+10 pts) labels Jul 25, 2026
@github-actions

Copy link
Copy Markdown

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

  • level:beginner — 20 pts
  • level:intermediate — 35 pts
  • level:advanced — 55 pts
  • level:critical — 80 pts

Quality (optional):

  • quality:clean — ×1.2 multiplier
  • quality:exceptional — ×1.5 multiplier

Validation (required to score):

  • gssoc:approved — counts for points
  • gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

@github-actions github-actions Bot added type:feature GSSoC type bonus: new feature type:design GSSoC type bonus: UI/design (+10 pts) type:performance GSSoC type bonus: performance (+15 pts) labels Jul 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gssoc26 GSSoC 2026 contribution type:bug GSSoC type bonus: bug fix type:design GSSoC type bonus: UI/design (+10 pts) type:docs GSSoC type bonus: documentation (+5 pts) type:feature GSSoC type bonus: new feature type:performance GSSoC type bonus: performance (+15 pts) type:testing GSSoC type bonus: tests (+10 pts)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] README Quick Start uses npm install but project requires pnpm — conflicts with committed pnpm-lock.yaml

1 participant