You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 30, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: .changeset/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
Hello and welcome! To manage our change log and releases, we use [Changesets](https://github.com/changesets/changesets) to [version](https://semver.org/) and publish code.
4
4
5
-
To add an entry to the change log for your pull request, from your feature branch run `yarn changeset` in your terminal. Use the arrow, spacebar, and return keys to answer the following Changesets CLI questions:
5
+
To add an entry to the change log for your pull request, from your feature branch run `pnpm changeset` in your terminal. Use the arrow, spacebar, and return keys to answer the following Changesets CLI questions:
`react` is now a required peerDependency (even when importing non-React SVG assets). [More info](https://github.com/Shopify/polaris/pull/11825#pullrequestreview-1974881032)
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,14 +85,14 @@ We’ll review your pull request and either merge it, request changes to it, or
85
85
**Before submitting a pull request**, please:
86
86
87
87
1. Fork the repository and create your branch from `main`
88
-
1. Run `yarn` in the repository root
88
+
1. Run `pnpm` in the repository root
89
89
1. If you’ve fixed a bug or added code, make sure to add tests
90
-
1. Ensure the test suite passes with `yarn test` (protip: `yarn test:watch TestName` is helpful in development)
91
-
1. Format your code with `yarn format`
92
-
1. Make sure your code lints with `yarn lint`
93
-
1. Run the TypeScript compiler with `yarn type-check`
94
-
1.[Tophat 🎩](https://github.com/Shopify/polaris/blob/main/documentation/Tophatting.md) your changes locally in Storybook with `yarn dev`
95
-
1. Create a changeset by running `yarn changeset`. [More info](https://github.com/Shopify/polaris/blob/main/.github/CONTRIBUTING.md#adding-a-changeset).
90
+
1. Ensure the test suite passes with `pnpm test` (protip: `pnpm test:watch TestName` is helpful in development)
91
+
1. Format your code with `pnpm format`
92
+
1. Make sure your code lints with `pnpm lint`
93
+
1. Run the TypeScript compiler with `pnpm type-check`
94
+
1.[Tophat 🎩](https://github.com/Shopify/polaris/blob/main/documentation/Tophatting.md) your changes locally in Storybook with `pnpm dev`
95
+
1. Create a changeset by running `pnpm changeset`. [More info](https://github.com/Shopify/polaris/blob/main/.github/CONTRIBUTING.md#adding-a-changeset).
96
96
1. If you haven’t already, [sign a CLA](https://cla.shopify.com/)
97
97
98
98
### Changelog
@@ -109,14 +109,14 @@ A changeset describes changes made in a branch or commit. It holds three bits of
109
109
110
110
Add a changeset if you have made any changes that will require a package version bump and release:
111
111
112
-
1. Run `yarn changeset`.
112
+
1. Run `pnpm changeset`.
113
113
2. Select the packages you want to include using ↑ and ↓ to navigate to packages, and space to select a package. Hit enter when all desired packages are selected.
114
114
3. Select a [bump type](https://github.com/Shopify/polaris/blob/main/.github/CONTRIBUTING.md#semantic-versioning) for each selected package.
115
115
4. Provide a message to be written into the changelog on the next release.
116
116
117
117
#### Writing a changelog message
118
118
119
-
Keep the following in mind when authoring your changelog entry (final prompt after running `yarn changeset`):
119
+
Keep the following in mind when authoring your changelog entry (final prompt after running `pnpm changeset`):
120
120
121
121
- Use a positive, conversational tone (for example, use “support” over “allow” and other authoritative verbs)
122
122
- Avoid redundancy when possible (try to phrase a bug fix entry without the word “bug”)
@@ -137,7 +137,7 @@ Each contributor is required to [sign a CLA](https://cla.shopify.com/). This pro
137
137
138
138
### Contribution prerequisites
139
139
140
-
- You have Node installed at v20.11.1+ and Yarn at v1.22.18+
140
+
- You have Node installed at v20.11.1+ and Pnpm at v8+
141
141
142
142
### Best practices
143
143
@@ -153,8 +153,8 @@ See the [README.md file](https://github.com/Shopify/polaris/blob/main/README.md#
153
153
154
154
We recommend running tests as well as trying your build of a package in a real project, to make sure you don’t introduce any regressions as you work on your change.
155
155
156
-
-`yarn test` will run tests for all packages
157
-
-`yarn turbo run test --filter="[HEAD^1]"` will test any package that has changed in the last commit
156
+
-`pnpm test` will run tests for all packages
157
+
-`pnpm turbo run test --filter="[HEAD^1]"` will test any package that has changed in the last commit
158
158
159
159
You can test your changes in another project locally by creating a [snapshot release](https://github.com/Shopify/polaris/blob/main/documentation/Releasing.md#snapshot-release).
160
160
@@ -163,16 +163,16 @@ On your feature branch PR, ensure you have a [changeset](https://github.com/Shop
163
163
Once the snapshot is ready, there will be a new comment in your feature PR with the newly released versions. In your external project, add the snapshot package or packages. An example snapshot package should have the following format:
Run the project as usual to tophat local changes. If you need to make updates, push new package changes to your feature PR and create a new snapshot release.
170
170
171
171
### Code style
172
172
173
-
We use an automatic code formatter called [Prettier](https://prettier.io/). Run `yarn format` after making any changes to the code.
173
+
We use an automatic code formatter called [Prettier](https://prettier.io/). Run `pnpm format` after making any changes to the code.
174
174
175
-
Linting will catch common issues that may exist in your code. You can check the status of your code styling by running `yarn lint`.
175
+
Linting will catch common issues that may exist in your code. You can check the status of your code styling by running `pnpm lint`.
176
176
177
177
Our code editor of choice is [VS Code](https://code.visualstudio.com/) which has [integrations with Prettier](https://github.com/prettier/prettier-vscode) and our linting tools which make this automatic. If you choose to use VS Code, these integrations will be listed as recommended extensions (or search for `@recommended`) in the extensions panel.
0 commit comments