Repository navigation
wp-now: add instructions for publishing to npm - #340
Conversation
|
Lovely, thank you! |
|
|
||
| ## Publishing to npm | ||
|
|
||
| The `wp-now` package is part of a larger monorepo, sharing its space with other sibiling packages. To publish the `wp-now` package to npm, you must first understand the automated release process facilitated by lerna. This process includes automatically incrementing the version number, creating a new tag, and publishing all modified packages to npm simultaneously. Notably, all published packages share the same version number. |
There was a problem hiding this comment.
Are any steps required here?
There was a problem hiding this comment.
Nope, Lerna does that automatically. The readme could be clearer about that though, @sejas
|
|
||
| Each package identifies a distinct organization in its `package.json` file. To publish the `wp-now` package, you need access to the npm organizations `@wp-playground`, `@php-wasm`, and `@wp-now`. | ||
|
|
||
| To initiate the publishing process for the all the modified packages, execute the following commands: |
There was a problem hiding this comment.
Should we make it possible to only publish a single package?
There was a problem hiding this comment.
Lerna detects changes and only publishes the ones that changed. It is not possible to publish just a single package when it depends on other packages from the monorepo. You can always use npm publish for that if you feel confident and also bump the versions, add tags etc manually.
There was a problem hiding this comment.
|
|
||
| The `wp-now` package is part of a larger monorepo, sharing its space with other sibiling packages. To publish the `wp-now` package to npm, you must first understand the automated release process facilitated by lerna. This process includes automatically incrementing the version number, creating a new tag, and publishing all modified packages to npm simultaneously. Notably, all published packages share the same version number. | ||
|
|
||
| Each package identifies a distinct organization in its `package.json` file. To publish the `wp-now` package, you need access to the npm organizations `@wp-playground`, `@php-wasm`, and `@wp-now`. |
There was a problem hiding this comment.
Who should publish releases?
There was a problem hiding this comment.
This is related to governance, I'll kick off that project soon.
What?
Add
Publishing to npmsection topackages/wp-now/README.mdWhy?
It was asked here #231 (comment)
How?
I described the publishing instricutions to the
wp-nowReadme.Testing Instructions
Publishing to npm