Document use of pnpm/turbo in readme #954
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per #952,
README.md
currently directs folks to install and build the project withyarn
. The project moved topnpm
about four weeks ago, so contributors will trip up if they follow the installation instructions as is, or realize there's apnpm-lock.yaml
file and not trust the README at all.I've swapped out
yarn
forpnpm
where I can (and also replaced thestart
command withdev
as well). However, the README also details a release process based on the old Lerna flow before moving to Turborepo. I'm not at all sure what the current release process is, so I'm leaving the PR as a draft until I get some feedback.