build: Swapping NPM for PNPM Step 4 of 5

.npmrc

@@ -1 +1,2 @@
-min-release-age=7
+min-release-age=7
+public-hoist-pattern[]=run-node

docs/README.md

@@ -17,20 +17,20 @@ developers to quickly build beautiful and consistent interfaces for our users.
 ### Prerequisites
 
 - `node@24`
-- `npm@11`
+- `pnpm@10`
 
 To install Atlantis locally for development:
 
 ```sh
 git clone git@github.com:GetJobber/atlantis.git
 cd atlantis
-npm install
+pnpm install
 ```
 
 To start local development for Atlantis:
 
 ```sh
-npm start
+pnpm start
 ```
 
 This starts the web Storybook, the mobile Storybook, and the docs site together.
@@ -50,14 +50,14 @@ will automatically take care of managing the versions for you.
 
 When working on some packages (for example `design`) locally, you'll need to run
 
-```
- npm run bootstrap
+```sh
+pnpm run bootstrap
 ```
 
 and then
 
-```
-  npm start
+```sh
+pnpm start
 ```
 
 to view and test your changes.
@@ -107,15 +107,15 @@ started.
 You should name your component in `PascalCase`.
 
 ```sh
-npm run generate
+pnpm run generate
 ```
 
 You will be able to select the platform you want to create the component.
 
 #### Example
 
 ```sh
-❯❯❯ npm run generate
+❯❯❯ pnpm run generate
 
 > atlantis@0.0.1 generate /path/to/atlantis
 > plop
@@ -142,28 +142,28 @@ You will be able to select the platform you want to create the component.
 To run tests:
 
 ```sh
-npm test
+pnpm test
 ```
 
 ### Linting
 
 To ensure your code passes our linters run:
 
 ```sh
-npm run lint
+pnpm run lint
 ```
 
 You can also auto fix many linting errors by running:
 
-```
-npm run lint:fix
+```sh
+pnpm run lint:fix
 ```
 
 You can run the linters separately with:
 
 ```sh
-npm run lint:css
-npm run lint:ts
+pnpm run lint:css
+pnpm run lint:js
 ```
 
 If you want to troubleshoot linting errors in CI, try running locally first to
@@ -186,10 +186,10 @@ The primary packages in here are:
 
 When installing dependencies be sure to install them relative to the appropriate
 sub package. For example if you want to use package `foo` in the components
-package, you would run `npm install foo -w @jobber/components`.
+package, you would run `pnpm --filter @jobber/components add foo`.
 
 For more information on how the packages are bootstrapped, check out
-[NPM workspaces](https://docs.npmjs.com/cli/v9/using-npm/workspaces).
+[pnpm workspaces](https://pnpm.io/workspaces).
 
 ## Contributing
 
@@ -206,7 +206,7 @@ publish whenever a pull request is merged.
 Follow [semver](https://semver.org) when choosing versions.
 
 ```sh
-npm run release-the-kraken
+pnpm run release-the-kraken
 ```
 
 ### Publishing a failed release to NPM
@@ -217,15 +217,15 @@ publish to NPM. If this happens and you're one of the Atlantis NPM
 collaborators, run the code below to send unpublished versions to NPM.
 
 ```sh
-npm run release:unpublished-package
+pnpm run release:unpublished-package
 ```
 
 ## Pre-release
 
 ### Releasing manually (Team Atlantis Only)
 
 ```sh
-npm run publish:prerelease
+pnpm run publish:prerelease
 ```
 
 ### Releasing with dependency changes
@@ -236,7 +236,7 @@ that as a releasable "change". The script below should allow you to create a
 prerelease for package changes.
 
 ```sh
-npm run publish:prerelease:force @jobber/components
+pnpm run publish:prerelease:force @jobber/components
 ```
 
 _NOTE: You can replace `@jobber/components` with the package you want to
@@ -253,7 +253,7 @@ It is possible to generate Pre-releases through GitHub Actions.
    `Publish Pre-release (Recommended)` option
 5. If you only have dependency changes run the `Force Publish <package>` to get
    those changes published. This is only needed if the only file modified is the
-   `package.json` or `package-lock.json`
+   `package.json` or `pnpm-lock.yaml`
 6. When the Action is finished your PR will have a comment with the new release
    versions
 
@@ -264,11 +264,11 @@ forced pre-release._
 ## Local testing
 
 If you're not sharing your changes with your peers yet and want a quicker way to
-check your changes, you can run `npm run pack {{scope}}` from the root folder
-against one of the workspaces.
+check your changes, you can run `pnpm run pack -- {{scope}}` from the root
+folder against one of the workspaces.
 
 ```sh
-npm run pack @jobber/components
+pnpm run pack -- @jobber/components
 ```
 
 That will create a `jobber-components-{{version}}.tgz` file on the root. You can

lerna.json

@@ -1,5 +1,6 @@
 {
   "version": "independent",
+  "npmClient": "pnpm",
   "packages": [
     "packages/*"
   ],
@@ -17,7 +18,7 @@
         "**/*.stories.tsx",
         "lerna.json",
         "package.json",
-        "package-lock.json",
+        "pnpm-lock.yaml",
         "CHANGELOG.md"
       ]
     }