chore: switch from npm to pnpm (#8514)

Author: benmccann

.github/workflows/ci.yml

@@ -24,23 +24,26 @@ jobs:
             os: ubuntu-latest
     steps:
       - uses: actions/checkout@v3
+      - uses: pnpm/[email protected]
       - uses: actions/setup-node@v3
         with:
           node-version: ${{ matrix.node-version }}
-          cache: npm
-      - run: npm install
-      - run: npm run test:integration
+          cache: pnpm
+      - run: pnpm install --frozen-lockfile
+      - run: node node_modules/puppeteer/install.js
+      - run: pnpm test:integration
         env:
           CI: true
   Lint:
     runs-on: ubuntu-latest
     timeout-minutes: 5
     steps:
       - uses: actions/checkout@v3
+      - uses: pnpm/[email protected]
       - uses: actions/setup-node@v3
         with:
-          cache: npm
-      - run: 'npm i && npm run lint'
+          cache: pnpm
+      - run: 'pnpm i && pnpm lint'
   Unit:
     runs-on: ${{ matrix.os }}
     timeout-minutes: 10
@@ -59,10 +62,11 @@ jobs:
             os: ubuntu-latest
     steps:
       - uses: actions/checkout@v3
+      - uses: pnpm/[email protected]
       - uses: actions/setup-node@v3
         with:
-          cache: npm
-      - run: npm install
+          cache: pnpm
+      - run: pnpm install
         env:
           SKIP_PREPARE: true
-      - run: npm run test:unit
+      - run: pnpm test:unit

CONTRIBUTING.md

@@ -72,9 +72,9 @@ Small pull requests are much easier to review and more likely to get merged.
 
 ### Installation
 
-1. Ensure you have [npm](https://www.npmjs.com/get-npm) installed.
-1. After cloning the repository, run `npm install` in the root of the repository.
-1. To start a development server, run `npm run dev`.
+1. Ensure you have [pnpm](https://pnpm.io/installation) installed.
+1. After cloning the repository, run `pnpm install` in the root of the repository.
+1. To compile in watch mode, run `pnpm dev`.
 
 ### Creating a branch
 
@@ -94,8 +94,8 @@ Test samples are kept in `/test/xxx/samples` folder.
 
 #### Running tests
 
-1. To run test, run `npm run test`.
-1. To run test for a specific feature, you can use the `-g` (aka `--grep`) option. For example, to only run test involving transitions, run `npm run test -- -g transition`.
+1. To run test, run `pnpm test`.
+1. To run test for a specific feature, you can use the `-g` (aka `--grep`) option. For example, to only run test involving transitions, run `pnpm test -- -g transition`.
 
 ##### Running solo test
 
@@ -106,11 +106,11 @@ Test samples are kept in `/test/xxx/samples` folder.
 ##### Updating `.expected` files
 
 1. Tests suites like `css`, `js`, `server-side-rendering` asserts that the generated output has to match the content in the `.expected` file. For example, in the `js` test suites, the generated js code is compared against the content in `expected.js`.
-1. To update the content of the `.expected` file, run the test with `--update` flag. (`npm run test --update`)
+1. To update the content of the `.expected` file, run the test with `--update` flag. (`pnpm test --update`)
 
 ### Style guide
 
-[Eslint](https://eslint.org) will catch most styling issues that may exist in your code. You can check the status of your code styling by simply running `npm run lint`.
+[Eslint](https://eslint.org) will catch most styling issues that may exist in your code. You can check the status of your code styling by simply running `pnpm lint`.
 
 #### Code conventions
 
@@ -122,8 +122,8 @@ Test samples are kept in `/test/xxx/samples` folder.
 Please make sure the following is done when submitting a pull request:
 
 1. Describe your **test plan** in your pull request description. Make sure to test your changes.
-1. Make sure your code lints (`npm run lint`).
-1. Make sure your tests pass (`npm run test`).
+1. Make sure your code lints (`pnpm lint`).
+1. Make sure your tests pass (`pnpm test`).
 
 All pull requests should be opened against the `master` branch. Make sure the PR does only one thing, otherwise please split it.
 

README.md

@@ -34,21 +34,21 @@ To install and work on Svelte locally:
 ```bash
 git clone https://github.com/sveltejs/svelte.git
 cd svelte
-npm install
+pnpm install
 ```
 
 > Do not use Yarn to install the dependencies, as the specific package versions in `package-lock.json` are used to build and test Svelte.
 
 To build the compiler and all the other modules included in the package:
 
 ```bash
-npm run build
+pnpm build
 ```
 
-To watch for changes and continually rebuild the package (this is useful if you're using [npm link](https://docs.npmjs.com/cli/link.html) to test out changes in a project locally):
+To watch for changes and continually rebuild the package (this is useful if you're using [`pnpm link`](https://pnpm.io/cli/link) to test out changes in a project locally):
 
 ```bash
-npm run dev
+pnpm dev
 ```
 
 The compiler is written in [TypeScript](https://www.typescriptlang.org/), but don't let that put you off — it's basically just JavaScript with type annotations. You'll pick it up in no time. If you're using an editor other than [Visual Studio Code](https://code.visualstudio.com/), you may need to install a plugin in order to get syntax highlighting and code hints, etc.
@@ -57,13 +57,13 @@ The compiler is written in [TypeScript](https://www.typescriptlang.org/), but do
 ### Running Tests
 
 ```bash
-npm run test
+pnpm test
 ```
 
 To filter tests, use `-g` (aka `--grep`). For example, to only run tests involving transitions:
 
 ```bash
-npm run test -- -g transition
+pnpm test -- -g transition
 ```