Skip to content

Commit

Permalink
update package publishing guide
Browse files Browse the repository at this point in the history
  • Loading branch information
felixroos committed Mar 23, 2023
1 parent 18d7222 commit 251be60
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 3 deletions.
9 changes: 8 additions & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -123,7 +123,14 @@ To publish all packages that have been changed since the last release, run:

```sh
npm login
npx lerna publish

# this will increment all the versions in package.json files of non private packages to selected versions
npx lerna version --no-private

# publish all packages inside /packages using pnpm! don't use lerna to publish!!
pnpm --filter "./packages/**" publish --dry-run

# the last command was only a dry-run, make sure everything looks ok, if yes, run the same command without flag
```

To manually publish a single package, increase the version in the `package.json`, then run `pnpm publish`.
Expand Down
5 changes: 3 additions & 2 deletions website/src/pages/technical-manual/packages.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -58,5 +58,6 @@ These packages provide bindings for different ways to output strudel patterns:

## Tools

- [pnpm workspaces](https://pnpm.io/)
- Publishing packages is done with [lerna](https://lerna.js.org/).
- [pnpm](https://pnpm.io/) for package management, workspaces and publishing
- [lerna](https://lerna.js.org/) for bumping versions
- see CONTRIBUTING.md for more info

0 comments on commit 251be60

Please sign in to comment.