Skip to content

fix: Complete PNPM migration and Node 24 update#1727

Draft
Copilot wants to merge 3 commits intomainfrom
copilot/migrate-to-pnpm-update-node
Draft

fix: Complete PNPM migration and Node 24 update#1727
Copilot wants to merge 3 commits intomainfrom
copilot/migrate-to-pnpm-update-node

Conversation

Copy link
Contributor

Copilot AI commented Feb 3, 2026

Completes migration to PNPM and standardizes on Node 24 across the codebase, building on #1725 (pnpm-lock.yaml) and #1719 (Node 24 update).

Changes

Package Management

  • Replaced all npm commands with pnpm equivalents in package.json scripts
  • Updated engine requirements: node: ">=24", pnpm: ">=9"
  • Removed package-lock.json files (18K+ lines), added to .gitignore

CI/CD

  • Added pnpm/action-setup@v2 to GitHub workflows
  • Updated cache strategy from npm to pnpm
  • Changed install commands: npm cipnpm install --frozen-lockfile

Docker

  • Updated base images: node:22-alpinenode:24-alpine
  • Enabled corepack for pnpm in all build stages
  • Updated lockfile references: package-lock.jsonpnpm-lock.yaml

Runtime

  • Updated .nvmrc: 2224

Example

// Before
"scripts": {
  "build:api": "cd mobile-api && npm run build",
  "install:api": "cd mobile-api && npm ci"
}

// After
"scripts": {
  "build:api": "cd mobile-api && pnpm run build",
  "install:api": "cd mobile-api && pnpm install --frozen-lockfile"
}
Original prompt

This section details on the original issue you should resolve

<issue_title>Migrate to PNPM and update node version</issue_title>
<issue_description>## Description

Review the code base and ensure:

  • All npm commands are changed to pnpm
  • The code base uses Node 24</issue_description>

Comments on the Issue (you are @copilot in this section)


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Co-authored-by: huyenltnguyen <25715018+huyenltnguyen@users.noreply.github.com>
Copilot AI changed the title [WIP] Migrate project to PNPM and update Node version Complete PNPM migration and Node 24 update Feb 3, 2026
Copilot AI requested a review from huyenltnguyen February 3, 2026 18:20
@huyenltnguyen huyenltnguyen changed the title Complete PNPM migration and Node 24 update fix: Complete PNPM migration and Node 24 update Feb 3, 2026
@huyenltnguyen
Copy link
Member

@Sembauke I've got Copilot prepared the changes, but would like to check if the addition of pnpm-lock file was intentional (#1725). If we are happy with npm then we can just keep using it and revert the pnpm-lock file.

@Nirajn2311
Copy link
Member

The API docker image build process is broken and needs to fixed

@Sembauke
Copy link
Member

It must have snuck in there by mistake. I happy to continue using npm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Migrate to PNPM and update node version

4 participants