[chore] Replace yarn package manager with pnpm (#7598)

Author: ggdouglas

.circleci/config.yml

@@ -12,60 +12,49 @@ aliases:
       environment:
         CHROME_BIN: "/usr/bin/google-chrome"
 
-  - &restore-node-modules-cache
-    name: Restore node_modules cache
-    key: v1-node-modules-{{ checksum "yarn.lock" }}
+  - &restore-pnpm-cache
+    name: Restore pnpm store cache
+    key: v1-pnpm-store-{{ checksum "pnpm-lock.yaml" }}
 
-  - &restore-yarn-cache
-    name: Restore Yarn global cache
-    key: v1-yarn-global
-
-  - &save-node-modules-cache
-    name: Save node_modules cache
-    paths:
-      - node_modules
-    key: v1-node-modules-{{ checksum "yarn.lock" }}
-
-  - &save-yarn-cache
-    name: Save Yarn global cache
+  - &save-pnpm-cache
+    name: Save pnpm store cache
     paths:
-      # see https://yarnpkg.com/configuration/yarnrc#globalFolder
-      - /.yarn/berry/global
-    key: v1-yarn-global
+      - ~/.local/share/pnpm/store
+    key: v1-pnpm-store-{{ checksum "pnpm-lock.yaml" }}
 
 jobs:
   checkout-code:
     docker: *docker-node-image
     steps:
       - checkout
-      - restore_cache: *restore-yarn-cache
-      - restore_cache: *restore-node-modules-cache
+      - restore_cache: *restore-pnpm-cache
       - run: sudo corepack enable
-      - run: yarn install --immutable
-      - run: yarn constraints
-      - save_cache: *save-node-modules-cache
-      - save_cache: *save-yarn-cache
+      - run: pnpm install --frozen-lockfile
+      - run: pnpm store prune
+      - save_cache: *save-pnpm-cache
       - persist_to_workspace:
           root: "."
-          paths: [packages/*/node_modules]
+          paths:
+            - node_modules
+            - packages/*/node_modules
 
   clean-lockfile:
     docker: *docker-node-image
     steps:
       - checkout
-      - restore_cache: *restore-node-modules-cache
+      - restore_cache: *restore-pnpm-cache
       - run: sudo corepack enable
-      - run: yarn dedupe --check
+      - run: pnpm install --frozen-lockfile
+      - run: pnpm dedupe --check
 
   compile:
     docker: *docker-node-image
     resource_class: xlarge
     steps:
       - checkout
-      - restore_cache: *restore-node-modules-cache
       - attach_workspace: { at: "." }
       - run: sudo corepack enable
-      - run: yarn compile --parallel=7
+      - run: pnpm compile --parallel=7
       - persist_to_workspace:
           root: "."
           paths:
@@ -79,10 +68,9 @@ jobs:
       NODE_ENV: test
     steps:
       - checkout
-      - restore_cache: *restore-node-modules-cache
       - attach_workspace: { at: "." }
       - run: sudo corepack enable
-      - run: yarn format-check
+      - run: pnpm format-check
 
   lint:
     docker: *docker-node-image
@@ -92,12 +80,13 @@ jobs:
       NODE_ENV: test
     steps:
       - checkout
-      - restore_cache: *restore-node-modules-cache
       - attach_workspace: { at: "." }
       - run: sudo corepack enable
       - run: mkdir -p ./reports/eslint ./reports/stylelint
       # types and lint rules should already be compiled since this job depends on the 'compile' job
-      - run: yarn lint
+      - run:
+          command: pnpm lint
+          no_output_timeout: 20m
       - store_test_results: { path: ./reports }
       - store_artifacts: { path: ./reports }
 
@@ -108,10 +97,9 @@ jobs:
       NODE_ENV: test
     steps:
       - checkout
-      - restore_cache: *restore-node-modules-cache
       - attach_workspace: { at: "." }
       - run: sudo corepack enable
-      - run: yarn dist --parallel=7
+      - run: pnpm dist --parallel=7
       - persist_to_workspace:
           root: "."
           paths: [packages/*/lib, packages/*/dist]
@@ -123,15 +111,14 @@ jobs:
     parallelism: 2
     steps:
       - checkout
-      - restore_cache: *restore-node-modules-cache
       - attach_workspace: { at: "." }
       - run: sudo corepack enable
       - run: mkdir -p ./reports
       - run:
           command: |
             case $CIRCLE_NODE_INDEX in \
-            0) yarn nx test @blueprintjs/eslint-plugin ;; \
-            1) yarn nx test @blueprintjs/stylelint-plugin ;; \
+            0) pnpm nx test @blueprintjs/eslint-plugin ;; \
+            1) pnpm nx test @blueprintjs/stylelint-plugin ;; \
             esac
           when: always
       - store_test_results: { path: ./reports }
@@ -145,7 +132,6 @@ jobs:
     parallelism: 6
     steps:
       - checkout
-      - restore_cache: *restore-node-modules-cache
       - attach_workspace: { at: "." }
       - run: sudo corepack enable
       # Use an explicit version of Chrome for better test reproducibility.
@@ -166,11 +152,11 @@ jobs:
           # see https://github.com/palantir/blueprint/issues/3616
           command: |
             case $CIRCLE_NODE_INDEX in \
-            0) yarn nx run-many -t test:typeCheck ;; \
-            1) yarn nx test:karma @blueprintjs/core ;; \
-            2) yarn nx test:karma @blueprintjs/datetime ;; \
-            4) yarn nx test:karma @blueprintjs/select ;; \
-            5) yarn nx test:karma @blueprintjs/table
+            0) pnpm nx run-many -t test:typeCheck ;; \
+            1) pnpm nx test:karma @blueprintjs/core ;; \
+            2) pnpm nx test:karma @blueprintjs/datetime ;; \
+            4) pnpm nx test:karma @blueprintjs/select ;; \
+            5) pnpm nx test:karma @blueprintjs/table
             esac
           when: always
       - store_test_results: { path: ./reports }
@@ -182,19 +168,17 @@ jobs:
       JUNIT_REPORT_PATH: reports
     steps:
       - checkout
-      - restore_cache: *restore-node-modules-cache
       - attach_workspace: { at: "." }
       - run: sudo corepack enable
       - run: mkdir ./reports
-      - run: yarn nx run-many -t test:iso
+      - run: pnpm nx run-many -t test:iso
       - store_test_results: { path: ./reports }
       - store_artifacts: { path: ./reports }
 
   deploy-preview:
     docker: *docker-node-image
     steps:
       - checkout
-      - restore_cache: *restore-node-modules-cache
       - attach_workspace: { at: "." }
       - store_artifacts: { path: packages/docs-app/dist }
       - store_artifacts: { path: packages/landing-app/dist }
@@ -206,7 +190,6 @@ jobs:
     docker: *docker-node-image
     steps:
       - checkout
-      - restore_cache: *restore-node-modules-cache
       - attach_workspace: { at: "." }
       - run: sudo corepack enable
       - run: mkdir ./artifacts
@@ -217,7 +200,6 @@ jobs:
     docker: *docker-node-image
     steps:
       - checkout
-      - restore_cache: *restore-node-modules-cache
       - attach_workspace: { at: "." }
       - run: sudo corepack enable
       - run: ./scripts/publish-npm-semver-tagged

.gitattributes

@@ -15,16 +15,10 @@ lerna-debug.log
 # Nx
 .nx/cache
 
-# Yarn
-# see https://yarnpkg.com/getting-started/qa#which-files-should-be-gitignored
-yarn-error.log
-.pnp.*
-.yarn/*
-!.yarn/patches
-!.yarn/plugins
-!.yarn/releases
-!.yarn/sdks
-!.yarn/versions
+# pnpm
+# pnpm-lock.yaml should be committed
+# see https://pnpm.io/git#lockfiles
+.pnpm-debug.log*
 
 # Sass
 .sass-cache/

.gitignore

@@ -3,5 +3,5 @@ generated/
 lib/
 dist/
 /site/
-yarn.lock
+pnpm-lock.yaml
 changelog/

.prettierignore

@@ -2,17 +2,18 @@
 
 ## Build/Test Commands
 
--   **Build**: `yarn compile` (all packages), `yarn nx compile @blueprintjs/core` (single package)
--   **Test all**: `yarn test`, `nx run-many -t test`
--   **Test single package**: `yarn nx test:karma @blueprintjs/core` or `cd packages/core && yarn test:karma`
--   **Distribute**: `yarn dist`, `yarn nx dist @blueprintjs/core` (single package)
--   **Lint**: `yarn lint`, `yarn lint-fix` (auto-fix), `yarn nx lint @blueprintjs/core` (single package)
--   **Format**: `yarn format`, `yarn format-check`
--   **Verify all**: `yarn verify` (compile + dist + test + lint + format-check)
+-   **Build**: `pnpm compile` (all packages), `pnpm nx compile @blueprintjs/core` (single package)
+-   **Test all**: `pnpm test`, `pnpm nx run-many -t test`
+-   **Test single package**: `pnpm nx test:karma @blueprintjs/core` or `cd packages/core && pnpm test:karma`
+-   **Distribute**: `pnpm dist`, `pnpm nx dist @blueprintjs/core` (single package)
+-   **Lint**: `pnpm lint`, `pnpm lint-fix` (auto-fix), `pnpm nx lint @blueprintjs/core` (single package)
+-   **Format**: `pnpm format`, `pnpm format-check`
+-   **Verify all**: `pnpm verify` (compile + dist + test + lint + format-check)
 
 ## Architecture
 
--   **Monorepo** using Yarn workspaces + Nx task runner
+-   **Monorepo** using pnpm workspaces + Nx task runner
+-   **Package manager**: pnpm v10.18.3 (strict dependency resolution)
 -   **Packages**: Core UI components in `packages/` - core, datetime, select, table, icons, colors
 -   **Apps**: docs-app (blueprintjs.com), demo-app, table-dev-app for development
 -   **Build tools**: karma-build-scripts, node-build-scripts, webpack-build-scripts

.yarn/patches/README.md

@@ -9,7 +9,7 @@ Looking for places to contribute to the codebase? Check out the
 
 ### Installation
 
-First, ensure you have a compatible version of [Node.js](https://nodejs.org/) and [Yarn](https://yarnpkg.com)
+First, ensure you have a compatible version of [Node.js](https://nodejs.org/) and [pnpm](https://pnpm.io)
 installed on your machine. We recommend using [nvm](https://github.com/nvm-sh/nvm) and running `nvm use` in
 the repo to switch to right version of Node.
 
@@ -25,9 +25,9 @@ build. Make sure you have an [SSH key set up with your Github account](https://d
 ```sh
 git clone [email protected]:<username>/blueprint.git
 cd blueprint
-yarn
-yarn compile
-yarn dist
+pnpm install
+pnpm compile
+pnpm dist
 ```
 
 ## Developing
@@ -43,12 +43,12 @@ A typical contributor workflow looks like this:
     - [Coding guidelines](https://github.com/palantir/blueprint/wiki/Coding-guidelines)
     - [Editor integration](https://github.com/palantir/blueprint/wiki/Editor-integration)
 5. Ensure your code **compiles properly** and is **tested**, **linted**, and **formatted**.
-    - Run `yarn compile` at the repo root to build all libraries.
-    - Run `yarn bundle` at the repo root to build the Blueprint documentation and other bundles.
-    - Add unit tests as necessary when fixing bugs or adding features; run them with `yarn test` in the relevant package directory.
-    - Linting is best handled by your editor for real-time feedback (see [Editor integration](https://github.com/palantir/blueprint/wiki/Editor-integration)). Run `yarn lint` to be 100% safe.
-    - TypeScript lint errors can often be automatically fixed by ESLint. Run lint fixes with `yarn lint-fix`.
-    - Code formatting is enforced using [Prettier](https://prettier.io/). These errors can be fixed in your editor through the Prettier extension (make sure you have set up the editor integrations linked above). **Formatting checks will not run** during the `yarn lint` package script. Instead, when using the CLI or in a CI environment you should run the `yarn format` script to fix all formatting issues across the Blueprint monorepo.
+    - Run `pnpm compile` at the repo root to build all libraries.
+    - Run `pnpm bundle` at the repo root to build the Blueprint documentation and other bundles.
+    - Add unit tests as necessary when fixing bugs or adding features; run them with `pnpm test` in the relevant package directory.
+    - Linting is best handled by your editor for real-time feedback (see [Editor integration](https://github.com/palantir/blueprint/wiki/Editor-integration)). Run `pnpm lint` to be 100% safe.
+    - TypeScript lint errors can often be automatically fixed by ESLint. Run lint fixes with `pnpm lint-fix`.
+    - Code formatting is enforced using [Prettier](https://prettier.io/). These errors can be fixed in your editor through the Prettier extension (make sure you have set up the editor integrations linked above). **Formatting checks will not run** during the `pnpm lint` package script. Instead, when using the CLI or in a CI environment you should run the `pnpm format` script to fix all formatting issues across the Blueprint monorepo.
 6. Submit a Pull Request on GitHub and fill out the template.
     - ⚠️ **DO NOT enable CircleCI for your fork of Blueprint.** When you open a PR, your branch will be checked out and built in palantir's CI pipeline automatically. There is no need to enable the CI build for your fork's pipeline. If you do, this may cause problems in the CI build.
         - If you have already opened a PR where CircleCI built the code in your own personal or organization pipeline, you will likely have to disable the project from building at app.circleci.com/settings/project/github/\<your-username\>/website and open a new PR.