chore: move to npm workspaces

Author: daKmoR

.github/workflows/canary.yml

@@ -25,27 +25,27 @@ jobs:
           FORCE_COLOR: 0
         with:
           node-version: '18'
-          cache: 'yarn'
+          cache: 'npm'
           registry-url: 'https://registry.npmjs.org'
 
       - name: Install Dependencies
-        run: yarn --frozen-lockfile
+        run: npm ci
 
       - name: Build packages
-        run: yarn build
+        run: npm run build
 
       - name: Build for production
-        run: yarn build:production
+        run: npm run build:production
 
       - name: Version canary release
-        run: yarn changeset version --snapshot canary
+        run: npx changeset version --snapshot canary
 
       - name: Release canary snapshots
         id: changesets
         uses: changesets/action@master
         with:
           # This expects you to have a script called release which does a build for your packages and calls changeset publish
-          publish: yarn changeset publish --tag canary
+          publish: npx changeset publish --tag canary
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

.github/workflows/release.yml

@@ -24,27 +24,27 @@ jobs:
           FORCE_COLOR: 0
         with:
           node-version: '18'
-          cache: 'yarn'
+          cache: 'npm'
           registry-url: 'https://registry.npmjs.org'
 
       - name: Install Dependencies
-        run: yarn --frozen-lockfile
+        run: npm ci
 
       - name: Build packages
-        run: yarn build
+        run: npm run build
 
       - name: Build for production
-        run: yarn build:production
+        run: npm run build:production
 
       - name: Sync blog to dev.to
-        run: DEV_TO_GIT_TOKEN=${{ secrets.DEV_TO_GIT_TOKEN }} yarn run dev-to-git
+        run: DEV_TO_GIT_TOKEN=${{ secrets.DEV_TO_GIT_TOKEN }} npm run run dev-to-git
 
       - name: Create Release Pull Request or Publish to npm
         id: changesets
         uses: changesets/action@master
         with:
           # This expects you to have a script called release which does a build for your packages and calls changeset publish
-          publish: yarn release
+          publish: npm run release
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

.github/workflows/verify-browserstack.yml

@@ -21,18 +21,18 @@ jobs:
           FORCE_COLOR: 0
         with:
           node-version: '18'
-          cache: 'yarn'
+          cache: 'npm'
 
       - name: Install dependencies
-        run: yarn --frozen-lockfile
+        run: npm ci
 
       - name: Build packages
-        run: yarn build
+        run: npm run build
 
       - name: Test
         run: |
           cd packages/test-runner-browserstack
-          yarn test
+          npm run test
         env:
           BROWSER_STACK_ACCESS_KEY: ${{ secrets.BROWSER_STACK_ACCESS_KEY }}
           BROWSER_STACK_USERNAME: ${{ secrets.BROWSER_STACK_USERNAME }}

.github/workflows/verify-node.yml

@@ -24,23 +24,23 @@ jobs:
           FORCE_COLOR: 0
         with:
           node-version: ${{ matrix.node-version }}
-          cache: yarn
+          cache: npm
 
       - name: Install Playwright dependencies
         run: npx playwright install-deps
 
       - name: Install dependencies
-        run: yarn --frozen-lockfile
+        run: npm ci
 
       - name: Build packages
-        run: yarn build
+        run: npm run build
 
       # build for production in CI to make sure tests can run with production build
       - name: Build for production
-        run: yarn build:production
+        run: npm run build:production
 
       - name: Lint
-        run: yarn lint
+        run: npm run lint
 
       - name: Test
-        run: yarn test
+        run: npm run test

.github/workflows/verify-saucelabs.yml

@@ -21,18 +21,18 @@ jobs:
           FORCE_COLOR: 0
         with:
           node-version: '18'
-          cache: 'yarn'
+          cache: 'npm'
 
       - name: Install dependencies
-        run: yarn --frozen-lockfile
+        run: npm ci
 
       - name: Build packages
-        run: yarn build
+        run: npm run build
 
       - name: Test
         run: |
           cd packages/test-runner-saucelabs
-          yarn test
+          npm run test
         env:
           SAUCE_ACCESS_KEY: ${{ secrets.SAUCE_ACCESS_KEY }}
           SAUCE_USERNAME: ${{ secrets.SAUCE_USERNAME }}

.github/workflows/verify-windows.yml

@@ -20,20 +20,20 @@ jobs:
           FORCE_COLOR: 0
         with:
           node-version: '18'
-          cache: 'yarn'
+          cache: 'npm'
 
       - name: Install Playwright dependencies
         run: npx playwright install-deps
 
       - name: Install dependencies
-        run: yarn --frozen-lockfile
+        run: npm ci
 
       - name: Build
-        run: yarn build
+        run: npm run build
 
       # build for production in CI to make sure tests can run with production build
       - name: Build for production
-        run: yarn build:production
+        run: npm run build:production
 
       - name: Test
-        run: yarn test
+        run: npm run test

.gitignore

@@ -20,8 +20,7 @@ yarn-error.log
 ## temp folders
 /.tmp/
 
-## we prefer yarn.lock
-package-lock.json
+yarn.lock
 ## lock files in packages we do not need to save
 packages/*/yarn.lock
 

.husky/pre-commit

@@ -1,4 +1,4 @@
 #!/bin/sh
 . "$(dirname "$0")/_/husky.sh"
 
-yarn lint-staged
+npx lint-staged

CONTRIBUTING.md

@@ -21,11 +21,11 @@ git remote add upstream git@github.com:modernweb-dev/web.git
 
 ## Preparing Your Local Environment for Development
 
-Now that you have cloned the repository, ensure you have [yarn](https://classic.yarnpkg.com/lang/en/) installed, then run the following command to set up the development environment.
+Now that you have cloned the repository, ensure you have node 18+ installed, then run the following command to set up the development environment.
 
 ```sh
-yarn install
-yarn build
+npm run install
+npm run build
 ```
 
 This will download and install all packages needed.
@@ -46,11 +46,11 @@ Commits are linted using precommit hooks, meaning that any code that raises a li
 
 ### Running Tests
 
-To run the tests of a package, it's recommended to `cd` into the package directory and then using `yarn test` to run them. This way you're only running tests of that specific package. The project needs to have been built at least once with `yarn build` for the tests to run.
+To run the tests of a package, it's recommended to `cd` into the package directory and then using `npm run test` to run them. This way you're only running tests of that specific package. The project needs to have been built at least once with `npm run build` for the tests to run.
 
 ### Adding New Packages
 
-For all projects, the tsconfig/jsconfig configuration files are auto-generated. You need to add an entry to the [./workspace-packages.mjs](./workspace-packages.mjs) to let it generate a config for you. After adding an entry, run `yarn update-package-configs` to generate the files for you.
+For all projects, the tsconfig/jsconfig configuration files are auto-generated. You need to add an entry to the [./workspace-packages.mjs](./workspace-packages.mjs) to let it generate a config for you. After adding an entry, run `npm run update-package-configs` to generate the files for you.
 
 ### Creating a Changeset
 
@@ -62,7 +62,7 @@ This documents your intent to release and allows you to specify a message that w
 To create a changeset, run:
 
 ```sh
-yarn changeset
+npx changeset
 ```
 
 Use the menu to select for which packages you need a release, and then select what kind of release. For the release type, we follow [Semantic Versioning](https://semver.org/), so please take a look if you're unfamiliar.

docs/blog/introducing-web-test-runner/index.md.review

@@ -141,7 +141,7 @@ This will locally install the required versions of Chromium, Firefox, and WebKit
 Now all we need to do is run our tests:
 
 ```
-$ yarn test
+$ npm run test
 $ web-test-runner "test/**/*.test.js" --node-resolve --playwright --browsers chromium firefox webkit
 
 Chromium: |██████████████████████████████| 2/2 test files | 3 passed, 0 failed