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
Copy file name to clipboardexpand all lines: DEVELOPMENT.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ Changesets will do most of the heavy lifting for our releases. When changes are
16
16
### Starting a new pre-release
17
17
18
18
- Ensure you are on the new `release-*` branch.
19
-
- Enter Changesets pre-release mode using the `pre` tag: `yarn changeset pre enter pre`.
19
+
- Enter Changesets pre-release mode using the `pre` tag: `pnpm changeset pre enter pre`.
20
20
- Commit the change and push the `release-*` branch to GitHub.
21
21
- Wait for the release workflow to finish. The Changesets action in the workflow will open a PR that will increment all versions and generate the changelogs.
22
22
- Review the updated `CHANGELOG` files and make any adjustments necessary, then merge the PR into the `release-*` branch.
@@ -32,7 +32,7 @@ Changesets will do most of the heavy lifting for our releases. When changes are
32
32
You may need to make changes to a pre-release prior to publishing a final stable release. To do so:
33
33
34
34
- Make whatever changes you need.
35
-
- Create a new changeset: `yarn changeset`.
35
+
- Create a new changeset: `pnpm changeset`.
36
36
-**IMPORTANT:** This is required even if you ultimately don't want to include these changes in the logs. Remember, changelogs can be edited prior to publishing, but the Changeset version script needs to see new changesets in order to create a new version.
37
37
- Commit the changesets and push the `release-*` branch to GitHub.
38
38
- Wait for the release workflow to finish and the Changesets action to open its PR that will increment all versions.
@@ -42,7 +42,7 @@ You may need to make changes to a pre-release prior to publishing a final stable
42
42
43
43
### Publishing the stable release
44
44
45
-
- Exit Changesets pre-release mode: `yarn changeset pre exit`.
45
+
- Exit Changesets pre-release mode: `pnpm changeset pre exit`.
46
46
- Commit the edited pre-release file along with any unpublished changesets, and push the `release-*` branch to GitHub.
47
47
- Wait for the release workflow to finish. The Changesets action in the workflow will open a PR that will increment all versions and generate the changelogs for the stable release.
48
48
- Review the updated `CHANGELOG` files and make any adjustments necessary.
@@ -71,6 +71,6 @@ Experimental releases and hot-fixes do not need to be branched off of `dev`. Exp
71
71
72
72
- Create a new branch for the release: `git checkout -b release-experimental`
73
73
- Make whatever changes you need and commit them: `git add . && git commit "experimental changes!"`
74
-
- Update version numbers and create a release tag: `yarn run version:experimental`
74
+
- Update version numbers and create a release tag: `pnpm run version:experimental`
75
75
- Push to GitHub: `git push origin --follow-tags`
76
76
- The CI workflow should automatically trigger from the experimental tag to publish the release to npm
Copy file name to clipboardexpand all lines: docs/guides/contributing.md
+10-10
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ cd react-router
30
30
git checkout dev
31
31
```
32
32
33
-
3. Install dependencies and build. React Router uses [`yarn` (version 1)](https://classic.yarnpkg.com/lang/en/docs/install), so you should too. If you install using `npm`, unnecessary `package-lock.json` files will be generated.
33
+
3. Install dependencies and build. React Router uses [pnpm](https://pnpm.io), so you should too. If you install using `npm`, unnecessary `package-lock.json` files will be generated.
34
34
35
35
## Think You Found a Bug?
36
36
@@ -72,22 +72,22 @@ All commits that change or add to the API must be done in a pull request that al
72
72
73
73
React Router uses a monorepo to host code for multiple packages. These packages live in the `packages` directory.
74
74
75
-
We use [Yarn workspaces](https://classic.yarnpkg.com/en/docs/workspaces/) to manage installation of dependencies and running various scripts. To get everything installed, make sure you have [Yarn (version 1) installed](https://classic.yarnpkg.com/lang/en/docs/install), and then run `yarn` or `yarn install` from the repo root.
75
+
We use [pnpm workspaces](https://pnpm.io/workspaces/) to manage installation of dependencies and running various scripts. To get everything installed, make sure you have [pnpm installed](https://pnpm.io/installation), and then run `pnpm install` from the repo root.
76
76
77
77
### Building
78
78
79
-
Calling `yarn build` from the root directory will run the build, which should take only a few seconds. It's important to build all the packages together because `react-router-dom` and `react-router-native` both use `react-router` as a dependency.
79
+
Calling `pnpm build` from the root directory will run the build, which should take only a few seconds. It's important to build all the packages together because `react-router-dom` and `react-router-native` both use `react-router` as a dependency.
80
80
81
81
### Testing
82
82
83
-
Before running the tests, you need to run a build. After you build, running `yarn test` from the root directory will run **every** package's tests. If you want to run tests for a specific package, use `yarn test --projects packages/<package-name>`:
83
+
Before running the tests, you need to run a build. After you build, running `pnpm test` from the root directory will run **every** package's tests. If you want to run tests for a specific package, use `pnpm test --projects packages/<package-name>`:
84
84
85
85
```bash
86
86
# Test all packages
87
-
yarntest
87
+
pnpmtest
88
88
89
89
# Test only react-router-dom
90
-
yarntest --projects packages/react-router-dom
90
+
pnpmtest --projects packages/react-router-dom
91
91
```
92
92
93
93
## Repository Branching
@@ -111,7 +111,7 @@ When it's time to cut a new release, we follow a process based on our branching
111
111
We create experimental releases from the current state of the `dev` branch. They can be installed by using the `@next` tag:
0 commit comments