Migrate to pnpm

.eslintignore

@@ -4,3 +4,4 @@
 
 dist/
 __fixtures__
+

.eslintrc

@@ -17,7 +17,7 @@
       }
     },
     {
-      "files": ["*.ts", "*.cts", "*.mts"],
+      "files": ["**/*.{ts,cts,mts}"],
       "parser": "@typescript-eslint/parser",
       "plugins": ["@typescript-eslint"],
       "extends": [

.github/workflows/ci.yml

@@ -24,13 +24,14 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
+      - uses: pnpm/action-setup@v2
       - uses: actions/setup-node@v4
         with:
-          node-version: 18
-          cache: yarn
+          cache: 'pnpm'
+      - run: pnpm install
+      - run: pnpm lint
+      - uses: wyvox/action-setup-pnpm@v3
 
-      - run: yarn install --frozen-lockfile
-      - run: yarn lint
 
 
   # tracking for re-enablement here: https://github.com/typed-ember/glint/issues/728
@@ -42,29 +43,32 @@ jobs:
   #     - uses: actions/setup-node@v4
   #       with:
   #         node-version: 18
-  #         cache: yarn
+  #         cache: pnpm
 
-  #     - run: yarn install --frozen-lockfile
-  #     - run: "yarn build"
-  #     - run: "yarn workspaces run test:typecheck"
-  #     - run: "yarn workspaces run test:tsc"
+  #     - uses: pnpm/action-setup@v2
+  #       with:
+  #         version: 10.6.2
+  #         run_install: true
+  #     - run: "pnpm build"
+  #     - run: "pnpm --filter '*' run test:typecheck"
+  #     - run: "pnpm --filter '*' run test:tsc"
 
   test:
     name: Test
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
+      - uses: pnpm/action-setup@v2
       - uses: actions/setup-node@v4
         with:
-          node-version: 18
-          cache: yarn
-      - run: yarn install --frozen-lockfile
-      - name: Build
-        run: yarn build
+          cache: 'pnpm'
+      - run: pnpm reset
       - name: Run Tests
         uses: coactions/setup-xvfb@v1
         with:
-          run: yarn test
+          run: pnpm test
+      - uses: wyvox/action-setup-pnpm@v3
+
 
   # The Windows runner can be super flaky both with Yarn installs and
   # when launching browser tests, so we allow for retries in those steps.
@@ -84,21 +88,23 @@ jobs:
   #       with:
   #         max_attempts: 2
   #         timeout_minutes: 10
-  #         command: yarn install --frozen-lockfile
+  #         command: pnpm install
   #     - name: Build
-  #       run: yarn build
+  #       run: pnpm build
   #     - name: Test @glint/core
   #       uses: nick-fields/retry@v2
   #       with:
   #         max_attempts: 2
   #         timeout_minutes: 20
-  #         command: yarn workspace @glint/core test
+  #         command: pnpm --filter @glint/core test
   #     - name: Test glint-vscode
   #       uses: nick-fields/retry@v2
   #       with:
   #         max_attempts: 2
   #         timeout_minutes: 10
-  #         command: yarn workspace glint-vscode test
+  #         command: pnpm --filter glint-vscode test
+  #     - name: Test @glint/scripts
+  #       run: pnpm --filter @glint/scripts test
 
   # tracking for re-enablement here: https://github.com/typed-ember/glint/issues/728
   # test-floating-deps:
@@ -109,14 +115,17 @@ jobs:
   #     - uses: actions/setup-node@v4
   #       with:
   #         node-version: 18
-  #         cache: yarn
-  #     - run: yarn install --no-lockfile
+  #         cache: 'pnpm'
+  #     - uses: pnpm/action-setup@v2
+  #       with:
+  #         version: 10.6.2
+  #         run_install: true
   #     - name: Build
-  #       run: yarn build
+  #       run: pnpm build
   #     - name: Run Tests
   #       uses: coactions/setup-xvfb@v1
   #       with:
-  #         run: yarn test
+  #         run: pnpm test
 
   # tracking for re-enablement here: https://github.com/typed-ember/glint/issues/728
   # test-ts-nightly:
@@ -127,12 +136,15 @@ jobs:
   #     - uses: actions/setup-node@v4
   #       with:
   #         node-version: 18
-  #         cache: yarn
-  #     - run: yarn install --frozen-lockfile
-  #     - run: yarn add --dev -W typescript@next
+  #         cache: 'pnpm'
+  #     - uses: pnpm/action-setup@v2
+  #       with:
+  #         version: 10.6.2
+  #         run_install: true
+  #     - run: pnpm add -D typescript@next
   #     - name: Build
-  #       run: yarn build
+  #       run: pnpm build
   #     - name: Run Tests
   #       uses: coactions/setup-xvfb@v1
   #       with:
-  #         run: yarn test
+  #         run: pnpm test

.github/workflows/publish-unstable.yml

@@ -25,21 +25,17 @@ jobs:
           node-version: 18
           # This creates an .npmrc that reads the NODE_AUTH_TOKEN environment variable
           registry-url: 'https://registry.npmjs.org'
-      - name: Locate Yarn Cache
-        id: yarn-cache-dir-path
-        run: echo "dir=$(yarn cache dir)" >> $GITHUB_OUTPUT
-      - uses: actions/cache@v3
+          cache: 'pnpm'
+
+      - uses: pnpm/action-setup@v2
         with:
-          path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
-          key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
-          restore-keys: |
-            ${{ runner.os }}-yarn-
-      - name: Install Dependencies
-        run: yarn install --frozen-lockfile
+          version: 10.6.2
+          run_install: true
+
       # - name: Lint
-      #   run: yarn lint
+      #   run: pnpm lint
       - name: Build
-        run: yarn build
+        run: pnpm build
 
 
       - name: set versions

.gitignore

@@ -1,5 +1,5 @@
 node_modules
-yarn-error.log
+pnpm-debug.log
 .eslintcache
 *.tsbuildinfo
 *.js.map

.npmrc

@@ -0,0 +1,80 @@
+ignore-scripts=true
+
+
+# Libraries should never have this enabled,
+# else we can break consumers
+auto-install-peers=false
+
+## Make sure we don't troll ourselves when updating deps
+##
+verify-deps-before-run=true
+
+
+## If a dependency is not declared, we do not want to accidentally
+## resolve it from the workspace root. This is a common source of
+## bugs in monorepos.
+##
+resolve-peers-from-workspace-root=false
+
+## We use so many similarly grouped peers, we want to make the
+## peer-groups easier to distinguish.
+## This forces a shorter sha for all groups (vs the default of 1000)
+##
+peers-suffix-max-length=40
+virtual-store-dir-max-length=40
+
+# We don't want to inject *all* dependencies.
+# only the ones that are peers. 
+inject-workspace-packages=false
+
+
+## This also means we do not want to hoist them to the root
+## As this would both expose them to all other packages AND
+## results in them using symlinks instead of hardlinks
+##
+hoist-workspace-packages=false
+
+
+## We use the `workspace:*` protocol for all workspace
+## packages.
+## In theory it would be nice to use `deep` here just in case
+## we missed something so that we could tell pnpm to use the
+## workspace version of a package if it exists. At any depth.
+##
+## However, it seems that deep/true result in workspace packages
+## that are dependencies being symlinked instead of hardlinked
+## more often, even at the top-level of a package, which is not
+## what we want.
+##
+link-workspace-packages=false # deep
+
+## Update injected dependencies when needed
+## This will rerun after various "build" scripts
+## In our published packages.
+##
+## Unfortunately, this does not run after scripts in
+## the monorepo root, so we have added a special "sync"
+## script to handle this.
+##
+sync-injected-deps-after-scripts[]=build
+sync-injected-deps-after-scripts[]=sync
+
+
+## In keeping with our "no hoisting" and "no auto-peers" and
+## "isolated dep trees", we also want to avoid other things
+## that lead to reliance on hoisting.
+## In general, deduping leads to hoisting. This particular
+## setting causes direct-dependencies to resolve from the
+## workspace root if already in root. We don't want this.
+##
+dedupe-direct-deps=false
+
+## We do not want to dedupe peer dependencies as this
+## results in hoisting and violates optional peer isolation.
+##
+dedupe-peer-dependents=false
+
+## We do not want to dedupe injected dependencies as this
+## results in hoisting and violates optional peer isolation.
+##
+dedupe-injected-deps=false

.prettierignore

@@ -2,6 +2,8 @@
 /packages/*/lib
 /test-packages/*/lib
 dist/
+*.yaml
+*.yml
 
 # Hidden directories
 .*/

.vscode/launch.json

@@ -5,7 +5,7 @@
       "name": "Debug Extension (Glint + TS)",
       "type": "extensionHost",
       "request": "launch",
-      // this errors. Run `yarn build` before launching this task
+      // this errors. Run `pnpm build` before launching this task
       // "preLaunchTask": "npm: build",
       "autoAttachChildProcesses": true,
       "runtimeExecutable": "${execPath}",
@@ -58,7 +58,7 @@
     // },
     {
       // For this to work, make sure you're runninc `tsc --build --watch` at the root, AND
-      // `yarn bundle:watch` from within vscode directory.
+      // `pnpm bundle:watch` from within vscode directory.
       "name": "Debug Extension (TS Plugin, .gts)",
       "type": "extensionHost",
       "request": "launch",
@@ -77,7 +77,7 @@
     },
     {
       // For this to work, make sure you're runninc `tsc --build --watch` at the root, AND
-      // `yarn bundle:watch` from within vscode directory.
+      // `pnpm bundle:watch` from within vscode directory.
       "name": "Debug Extension (TS Plugin, ember-app-loose-and-gts)",
       "type": "extensionHost",
       "request": "launch",

CONTRIBUTING.md

@@ -8,12 +8,13 @@ We welcome contributions to Glint! To help us help you be successful, please fol
 
 ## Working on the project
 
-Glint is a family of packages which all live in this repo as a Yarn workspace. To be most successful here, you should:
+Glint is a family of packages which all live in this repo as a pnpm workspace. To be most successful here, you should:
 
-- Install [Volta](https://volta.sh), a JavaScript toolchain manager we use to make sure everyone working on the project is using the same versions of Node and Yarn.
+- Install [Volta](https://volta.sh), a JavaScript toolchain manager we use to make sure everyone working on the project is using the same versions of Node and pnpm.
 - Clone the repo.
-- Run `yarn` in the root of the repo to install all the package dependencies. If you have Volta installed, it will automatically fetch and use the correct versions of Node and Yarn for you.
-- Run `yarn build` in the root of the repository to build all of the projects the first time. This will make sure that once you start working on one of the packages, you are working with an up to date version of the other packages in the project it depends on.
+- Run `pnpm install` in the root of the repo to install all the package dependencies. If you have Volta installed, it will automatically fetch and use the correct versions of Node and pnpm for you.
+- Run `pnpm build` in the root of the repository to build all of the projects the first time. This will make sure that once you start working on one of the packages, you are working with an up to date version of the other packages in the project it depends on.
+- Before running tests, you may need to make sure either `pnpm build` ( or `pnpm sync` if you're using `pnpm build --watch` in a separate terminal) is ran. This "installs" the core dependencies into the test packages so that peerDependencies resolve correctly.
 - Read the project’s [ARCHITECTURE.md](./ARCHITECTURE.md) to understand the basics of how the code base works.
 
 Once you have made changes and added tests to confirm they work correctly, you can then open a PR and we'll work with you to polish it up and get it landed!
@@ -53,7 +54,7 @@ These launch configurations can be run via the Run and Debug tab in VSCode.
 Firstly, there is an entire suite of integration tests that will spin up instances of VSCode and test out the VSCode Glint extension. These can be run from the `packages/vscode` directory via:
 
 ```
-yarn run test
+pnpm run test
 ```
 
 Secondly, the Launch Configurations described above (I believe) will run your client-side extension code in debug mode, along with the language server.

docs/ember/installation.md

@@ -6,10 +6,17 @@ To use Glint with [Ember](https://github.com/emberjs/ember.js) v3.24 or higher,
 Read on for a more detailed explanation of each of these steps.
 
 {% tabs %}
+{% tab title="pnpm" %}
+
+```sh
+pnpm add -D @glint/core @glint/template @glint/environment-ember-loose
+```
+
+{% endtab %}
 {% tab title="Yarn" %}
 
 ```sh
-yarn add --dev @glint/core @glint/template @glint/environment-ember-loose
+pnpm add -D @glint/core @glint/template @glint/environment-ember-loose
 ```
 
 {% endtab %}

docs/ember/template-imports.md

@@ -5,10 +5,17 @@ When adding Glint to an Ember project with `ember-template-imports` installed, t
 In addition to the `@glint/core`, `@glint/template` and `@glint/environment-ember-loose` packages, you also need to install the `@glint/environment-ember-template-imports` package and configure it in `tsconfig.json` under `glint.environment`:
 
 {% tabs %}
+{% tab title="pnpm" %}
+
+```sh
+pnpm add -D @glint/core @glint/template @glint/environment-ember-loose @glint/environment-ember-template-imports
+```
+
+{% endtab %}
 {% tab title="Yarn" %}
 
 ```sh
-yarn add --dev @glint/core @glint/template @glint/environment-ember-loose @glint/environment-ember-template-imports
+pnpm add -D @glint/core @glint/template @glint/environment-ember-loose @glint/environment-ember-template-imports
 ```
 
 {% endtab %}

docs/with-js.md

@@ -13,9 +13,15 @@ We do mean _identical_: unlike most existing JavaScript projects, you will need
 Thus, installation for a JS setup looks like this:
 
 {% tabs %}
+{% tab title="pnpm" %}
+```shell-session
+pnpm add -D typescript @glint/core @glint/template @glint/environment-ember-loose
+```
+{% endtab %}
+
 {% tab title="Yarn" %}
 ```shell-session
-yarn add --dev typescript @glint/core @glint/template @glint/environment-ember-loose
+pnpm add -D typescript @glint/core @glint/template @glint/environment-ember-loose
 ```
 {% endtab %}