chore: Migrate from npm to pnpm

.github/workflows/ci.yml

@@ -16,29 +16,33 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+      - name: Install pnpm
+        uses: pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v5
       - uses: actions/setup-node@53b83947a5a98c8d113130e565377fae1a50d02f # v6
         with:
           node-version: 'lts/*'
-          cache: 'npm'
+          cache: 'pnpm'
 
       - name: Install dependencies
-        run: npm ci
+        run: pnpm install --frozen-lockfile
 
       - name: Build
         run: |
-          npm run build
+          pnpm run build
 
   test:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+      - name: Install pnpm
+        uses: pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v5
       - uses: actions/setup-node@53b83947a5a98c8d113130e565377fae1a50d02f # v6
         with:
           node-version: 'lts/*'
-          cache: 'npm'
+          cache: 'pnpm'
 
       - name: Install dependencies
-        run: npm ci
+        run: pnpm install --frozen-lockfile
 
       -
         # Required for the package command tests to work
@@ -47,36 +51,40 @@ jobs:
 
       - name: Test
         run: |
-          npm test
+          pnpm test
 
   lint:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+      - name: Install pnpm
+        uses: pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v5
       - uses: actions/setup-node@53b83947a5a98c8d113130e565377fae1a50d02f # v6
         with:
           node-version: 'lts/*'
-          cache: 'npm'
+          cache: 'pnpm'
 
       - name: Install dependencies
-        run: npm ci
+        run: pnpm install --frozen-lockfile
 
       - name: Lint
         run: |
-          npm run lint
+          pnpm run lint
 
   format:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+      - name: Install pnpm
+        uses: pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v5
       - uses: actions/setup-node@53b83947a5a98c8d113130e565377fae1a50d02f # v6
         with:
           node-version: 'lts/*'
-          cache: 'npm'
+          cache: 'pnpm'
 
       - name: Install dependencies
-        run: npm ci
+        run: pnpm install --frozen-lockfile
 
       - name: Format
         run: |
-          npm run format:check
+          pnpm run format:check

Dockerfile

@@ -1,27 +1,31 @@
-FROM node:24-slim as builder
+FROM node:24-slim AS builder
+
+RUN corepack enable && corepack prepare pnpm@10.23.0 --activate
 
 WORKDIR /app
 
-COPY package*.json ./
+COPY package.json pnpm-lock.yaml ./
 
-RUN npm ci
+RUN pnpm install --frozen-lockfile
 
 COPY . .
 
-RUN npm run build
+RUN pnpm run build
 
 FROM node:24-slim AS final
 
+RUN corepack enable && corepack prepare pnpm@10.23.0 --activate
+
 WORKDIR /app
 
 COPY --from=builder ./app/dist ./dist
 
-COPY package*.json ./
+COPY package.json pnpm-lock.yaml ./
 
-RUN npm ci --omit=dev
+RUN pnpm install --frozen-lockfile --prod
 
 EXPOSE 7777
 
 ENTRYPOINT ["node", "dist/main.js"]
 
-CMD [ "serve", "--address", "[::]:7777", "--log-format", "json", "--log-level", "info" ]
+CMD [ "serve", "--address", "[::]:7777", "--log-format", "json", "--log-level", "info" ]

README.md

@@ -10,13 +10,13 @@ Read about how to build a new CloudQuery plugin from this template in [Creating
 Install dependencies
 
 ```shell
-npm install
+pnpm install
 ```
 
 Run the plugin locally
 
 ```shell
-npm run dev
+pnpm dev
 ```
 
 Run cloudquery
@@ -30,7 +30,7 @@ This will create db.sql file (a Sqlite database) with a table `Names` and two re
 ## Building and publishing the plugin
 
 1. Update the plugin metadata in [src/plugins.ts](src/plugin.ts#L99) to match your team and plugin name.
-2. Run `npm run build` to build the plugin.
+2. Run `pnpm build` to build the plugin.
 3. Run `node dist/main.js package -m "Initial release" v0.0.1 .`. `-m` specifies changelog and `v0.0.1` is the version.
 4. Run `cloudquery plugin publish -f` to publish the plugin to the CloudQuery registry.