这是indexloc提供的服务，不要输入任何密码
Skip to content

Fix Changesets references in the docs #132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 9, 2021
Merged

Fix Changesets references in the docs #132

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/pages/docs/guides/complimentary-tools.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,9 @@ Below is a running list of additional monorepo tools that you may find useful in

## Versioning, Publishing, and Changelog Generation

For the foreseable future, `turbo` is not going to deal with package publishing. Versioning/Publishing is an extremely opinionated topic with a lot of existing solutions. Our advice is to avoid versioning packages altogether unless you actually need to publish them to NPM for external consumption. If you have to version your packages, we really like the workflow of changesets (especially for open source projects).
For the foreseable future, `turbo` is not going to deal with package publishing. Versioning/Publishing is an extremely opinionated topic with a lot of existing solutions. Our advice is to avoid versioning packages altogether unless you actually need to publish them to NPM for external consumption. If you have to version your packages, we really like the workflow of Changesets (especially for open source projects).

- [atlassian/changesets](https://github.com/atlassian/changesets) - 🦋 A way to manage your versioning and changelogs with a focus on monorepos
- [changesets/changesets](https://github.com/changesets/changesets) - 🦋 A way to manage your versioning and changelogs with a focus on monorepos
- [microsoft/beachball](https://github.com/microsoft/beachball) - The Sunniest Semantic Version Bumper
- [lerna/lerna](https://github.com/lerna/lerna) - A tool for managing JavaScript projects with multiple packages.
- [lerna/lerna-changelog](https://github.com/lerna/lerna-changelog) - PR-based changelog generator with monorepo support
Expand Down
2 changes: 1 addition & 1 deletion docs/pages/docs/guides/migrate-from-lerna.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ The above may not not look like much. But imagine that A's `build` task takes 20

### Package Publishing, Versioning, and Changelog Generation

Lerna can version and publish packages to NPM registries as well as create changelogs. It's extremely good at this, especially for releasing canary pre-releases. While Turborepo may eventually tackle these features, at the time of writing, it is not a high priority goal (we suggest using using [atlassian/changesets](https://github.com/atlassian/changesets) in the meantime). If changesets isn't for you, and you want to stick with Lerna's publish flow, you can use Lerna and Turborepo together.
Lerna can version and publish packages to NPM registries as well as create changelogs. It's extremely good at this, especially for releasing canary pre-releases. While Turborepo may eventually tackle these features, at the time of writing, it is not a high priority goal (we suggest using using [Changesets](https://github.com/changesets/changesets) in the meantime). If Changesets isn't for you, and you want to stick with Lerna's publish flow, you can use Lerna and Turborepo together.

## Example migration

Expand Down