chore: switch from yarn to npm (#9575)

Yarn is confusing to newcomers and doesn't provide as much value
anymore.

---------

Co-authored-by: GitHub Actions Bot <[email protected]>

Author: domoritz

.github/PULL_REQUEST_TEMPLATE.md

@@ -5,7 +5,7 @@
 
 - [ ] This PR is atomic (i.e., it fixes one issue at a time).
 - [ ] The title is a concise [semantic commit message](https://www.conventionalcommits.org/) (e.g. "fix: correctly handle undefined properties").
-- [ ] `yarn test` runs successfully
+- [ ] `npm test` runs successfully
 - For new features:
   - [ ] Has unit tests.
   - [ ] Has documentation under `site/docs/` + examples.

.github/workflows/check-toc.yml

@@ -23,19 +23,19 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v4
         with:
-          cache: 'yarn'
+          cache: 'npm'
           node-version: 20
 
       - name: Install Node dependencies
-        run: yarn --frozen-lockfile
+        run: npm ci
 
       - name: Setup Ruby
         uses: ruby/setup-ruby@v1
         with:
           ruby-version: '3.4'
 
       - name: Setup data
-        run: yarn data
+        run: npm run data
 
       - name: Build Jekyll
         run: |

.github/workflows/check.yml

@@ -18,14 +18,14 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v4
         with:
-          cache: 'yarn'
+          cache: 'npm'
           node-version: 20
 
       - name: Install Node dependencies
-        run: yarn --frozen-lockfile
+        run: npm ci
 
       - name: Setup data
-        run: yarn data
+        run: npm run data
 
       - name: Install Parallel
         run: |
@@ -36,10 +36,10 @@ jobs:
           sudo mv parallel sem /usr/local/bin
 
       - name: Format
-        run: yarn format
+        run: npm run format
 
       - name: Build Schema
-        run: yarn schema
+        run: npm run schema
 
       - name: Check Schema
         run: scripts/check-schema.sh

.github/workflows/release-docs-and-schema.yml

@@ -25,14 +25,14 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v4
         with:
-          cache: 'yarn'
+          cache: 'npm'
           node-version: 20
 
       - name: Install Node dependencies
-        run: yarn --frozen-lockfile
+        run: npm ci
 
       - name: Build
-        run: yarn schema
+        run: npm run schema
 
       - name: Setup Git remote
         run: scripts/setup-git-ci.sh
@@ -61,17 +61,17 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v4
         with:
-          cache: 'yarn'
+          cache: 'npm'
           node-version: 20
 
       - name: Setup Pages
         uses: actions/configure-pages@v5
 
       - name: Install Node dependencies
-        run: yarn --frozen-lockfile
+        run: npm ci
 
       - name: Prebuild website
-        run: yarn presite
+        run: npm run presite
 
       - name: Build with Jekyll
         uses: actions/jekyll-build-pages@v1

.github/workflows/test-docs.yml

@@ -5,7 +5,7 @@ on:
   pull_request:
     paths:
       - 'site/**'
-      - 'yarn.lock'
+      - 'package-lock.json'
       - '**prettier**'
 
 jobs:
@@ -19,14 +19,14 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v4
         with:
-          cache: 'yarn'
+          cache: 'npm'
           node-version: 20
 
       - name: Install Node dependencies
-        run: yarn --frozen-lockfile
+        run: npm ci
 
       - name: Lint
-        run: yarn prettier . --check
+        run: npx prettier . --check
 
       - name: Build
-        run: yarn build:site
+        run: npm run build:site

.github/workflows/test.yml

@@ -18,20 +18,20 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v4
         with:
-          cache: 'yarn'
+          cache: 'npm'
           node-version: 20
 
       - name: Install Node dependencies
-        run: yarn --frozen-lockfile
+        run: npm ci
 
       - name: Tests
-        run: yarn vitest run test/
+        run: npx vitest run test/
 
       - name: Example tests
-        run: yarn vitest run examples/
+        run: npx vitest run examples/
 
       - name: Build
-        run: yarn build
+        run: npm run build
 
   runtime-lint-coverage:
     name: Runtime, Linting, and Coverage
@@ -43,32 +43,32 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v4
         with:
-          cache: 'yarn'
+          cache: 'npm'
           node-version: 20
 
       - name: Install Node dependencies
-        run: yarn --frozen-lockfile
+        run: npm ci
 
       - name: Copy Data
-        run: yarn data
+        run: npm run data
 
       - name: Set up playwright
-        run: yarn playwright install chromium
+        run: npx playwright install chromium
 
       - name: Build
-        run: yarn build:only
+        run: npm run build:only
 
       - name: Typechecks
-        run: yarn tsc
+        run: npx tsc
 
       - name: Lint
-        run: yarn lint
+        run: npm run lint
 
       - name: Runtime tests
-        run: yarn test:runtime --browser.headless
+        run: npm run test:runtime -- --browser.headless
 
       - name: Test coverage
-        run: yarn test:cover
+        run: npm run test:cover
 
       - name: Upload coverage to Codecov
         uses: codecov/[email protected]
@@ -90,14 +90,14 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v4
         with:
-          cache: 'yarn'
+          cache: 'npm'
           node-version: 20
 
       - name: Install Node dependencies
-        run: yarn --frozen-lockfile
+        run: npm ci
 
       - name: Build
-        run: yarn build:only
+        run: npm run build:only
 
       - name: Compile Vega
         run: |

.gitignore

@@ -3,7 +3,6 @@ _site/
 !site/examples/index.md
 .DS_Store
 .jekyll-metadata
-.yarnclean
 build/*
 coverage
 examples/all-examples.json
@@ -18,5 +17,3 @@ site/static/bundle.*
 test/log
 test/log/difflist.json
 test-runtime/__screenshots__
-yarn-debug.log*
-yarn-error.log*

.release-it.json

@@ -8,7 +8,7 @@
     "release": true
   },
   "hooks": {
-    "after:bump": "yarn build"
+    "after:bump": "npm build"
   },
   "plugins": {
     "@release-it/conventional-changelog": {

CONTRIBUTING.md

@@ -44,9 +44,9 @@ You can find [tasks with the "Good first issue" label in the issue tracker :pray
 
 The website is under `site/` and the documentation is under `site/docs/`. We use GitHub Pages to publish our documentation when we release a new version. To contribute changes to the documentation or website, simply submit a pull request that changes the corresponding markdown files in `site/`.
 
-Since we only publish the GitHub Pages when we release a new version, it might be slightly outdated compared to `main`. For development, once you have [setup the repository](#repository-setup), you can run `yarn site` to serve the GitHub page locally at [http://localhost:4000/vega-lite/](http://localhost:4000/vega-lite/).
+Since we only publish the GitHub Pages when we release a new version, it might be slightly outdated compared to `main`. For development, once you have [setup the repository](#repository-setup), you can run `npm run site` to serve the GitHub page locally at [http://localhost:4000/vega-lite/](http://localhost:4000/vega-lite/).
 
-Note that when you checkout different branches, the compiled JavaScript for the website might be reset. You might have to run `yarn build:site` to recompile the JavaScript so that interactive examples work.
+Note that when you checkout different branches, the compiled JavaScript for the website might be reset. You might have to run `npm run build:site` to recompile the JavaScript so that interactive examples work.
 
 ### Documentation Guide
 
@@ -84,13 +84,13 @@ To name the example file:
 - For interactive example, begin with either `interactive_` or `selection_`.
 - For examples that are only for regression test, begin with `test_`.
 
-After you push a new branch to GitHub, the CI will automatically run `yarn build:examples` to recompile all examples and push the changed Vega specs and SVG files in `examples/compiled` , so that your branch includes these changes. When you add a new example or update the code, you may run `yarn build:examples` or `yarn build:example <examplename>` (e.g., `yarn build:example bar_1d`) to see the change locally. However, do **not** include these changes in your commit as different systems produce slightly different SVGs (mainly due to floating point differences). To avoid unnecessary SVG diffs, we should just let the CI generate the images. You're still encouraged to run `yarn build:examples` to make sure that your code does not cause unnecessary changes.
+After you push a new branch to GitHub, the CI will automatically run `npm run build:examples` to recompile all examples and push the changed Vega specs and SVG files in `examples/compiled` , so that your branch includes these changes. When you add a new example or update the code, you may run `npm run build:examples` or `npm run build:example <examplename>` (e.g., `npm run build:example bar_1d`) to see the change locally. However, do **not** include these changes in your commit as different systems produce slightly different SVGs (mainly due to floating point differences). To avoid unnecessary SVG diffs, we should just let the CI generate the images. You're still encouraged to run `npm run build:examples` to make sure that your code does not cause unnecessary changes.
 
 **Notes:**
 
-1. `yarn build:examples` only re-compile SVGs if the output Vega file changes (so it runs way faster). If you want to enforce re-compilation of all SVGs, use `yarn build:examples-full`.
-2. To make Travis run `yarn build:examples-full`, include `[SVG]` in your commit message of the last commit in your branch.
-3. To run `yarn build:examples`, you need to install [gnu parallel](https://www.gnu.org/software/parallel/). (For Mac, you can simply do `brew install parallel`.)
+1. `npm run build:examples` only re-compile SVGs if the output Vega file changes (so it runs way faster). If you want to enforce re-compilation of all SVGs, use `npm run build:examples-full`.
+2. To make the CI run `npm run build:examples-full`, include `[SVG]` in your commit message of the last commit in your branch.
+3. To run `npm run build:examples`, you need to install [gnu parallel](https://www.gnu.org/software/parallel/). (For Mac, you can simply do `brew install parallel`.)
 
 # Development Guide
 
@@ -102,12 +102,12 @@ After you push a new branch to GitHub, the CI will automatically run `yarn build
 brew install node
 ```
 
-2. Clone this repository and cd into your local clone of the repository, and install all the npm dependencies. We use [yarn](https://yarnpkg.com/) to have reproducible dependencies:
+2. Clone this repository and cd into your local clone of the repository, and install all the npm dependencies:
 
 ```sh
 git clone https://github.com/vega/vega-lite.git
 cd vega-lite
-yarn
+npm install
 ```
 
 Now you should be able to build and test the code.
@@ -176,25 +176,25 @@ This section lists commands that are commonly used during development. See `pack
 
 ### Build
 
-You can run `yarn build` to compile Vega-Lite and regenerate `vega-lite-schema.json`.
+You can run `npm run build` to compile Vega-Lite and regenerate `vega-lite-schema.json`.
 
 ### Basic Lint & Test & Test Coverage
 
-`yarn test` run linting and all unit-tests respectively. `yarn format` automatically fixes linting issues if possible.
+`npm test` run linting and all unit-tests respectively. `npm run format` automatically fixes linting issues if possible.
 
-`yarn test:cover` includes test coverage and generates a report inside `coverage/index.html`. You can see if specific lines are covered in the unit test by running `open coverage/index.html` and browsing through the report.
+`npm run test:cover` includes test coverage and generates a report inside `coverage/index.html`. You can see if specific lines are covered in the unit test by running `open coverage/index.html` and browsing through the report.
 
 ### Watch tasks
 
 During development, it can be convenient to rebuild automatically or to run tests in the background. You can use:
 
-- `yarn watch` to start a watcher task that **re-compiles Vega-Lite** when `.ts` files related to VL change.
+- `npm run watch` to start a watcher task that **re-compiles Vega-Lite** when `.ts` files related to VL change.
 
-To automatically run tests when files change, run `yarn vitest`. You can also run specific tests like the runtime tests with `yarn vitest test-runtime/`.
+To automatically run tests when files change, run `npx vitest`. You can also run specific tests like the runtime tests with `npx vitest test-runtime/`.
 
 ### Website
 
-`yarn site`. See details in [Documentation and Website](#documentation-and-website).
+`npm run site`. See details in [Documentation and Website](#documentation-and-website).
 
 ### Publishing
 
@@ -213,11 +213,11 @@ We use the [Visual Studio Code](https://code.visualstudio.com/) editor.
 
 To manually test your changes locally, you should have a local instance of [Vega Editor](https://github.com/vega/editor) and link Vega-Lite to the editor (See [Vega Editor's README](https://github.com/vega/editor#local-testing--debugging) for instructions).
 
-To update the Vega-Lite code in the editor, you need to compile TypeScript to JavaScript. The easiest way is to run `yarn watch` in the Vega-Lite directory. This command will automatically recompile the code whenever you make changes.
+To update the Vega-Lite code in the editor, you need to compile TypeScript to JavaScript. The easiest way is to run `npm run watch` in the Vega-Lite directory. This command will automatically recompile the code whenever you make changes.
 
 ## Pull Requests and Continuous Integration (CI)
 
-All pull requests will be tested on [GitHub Actions](https://github.com/features/actions). If your PR does not pass the checks, your PR will not be approved. The CI will run `yarn test`, generate Vega specs and SVG files from your updated code, compare them with the existing compiled outputs in `examples/compiled/`, and check code coverage of your code. If you don't want your PR reviewed until checks pass, mark the [pull request as draft](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests). Once you're ready for review, convert the pull request to mark it as ready for review.
+All pull requests will be tested on [GitHub Actions](https://github.com/features/actions). If your PR does not pass the checks, your PR will not be approved. The CI will run `npm test`, generate Vega specs and SVG files from your updated code, compare them with the existing compiled outputs in `examples/compiled/`, and check code coverage of your code. If you don't want your PR reviewed until checks pass, mark the [pull request as draft](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests). Once you're ready for review, convert the pull request to mark it as ready for review.
 
 ### Code Coverage
 

examples/compiled/vega_version

@@ -1 +1 @@
-vega: 6.0.0
+vega: 6.1.2