Add option packToPath to pack packages instead of publishing #935
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.
Add an option
packToPath
to support the new workflow of using an ADO task to publish to npm. If this option is provided, the actual publish step will be skipped, and insteadnpm pack
will be called on each package (with the resulting files moved to the specified directory).Usage from command line (could also be in a config file):
beachball publish --packToPath /somewhere/my-pack-dir
The files in the pack directory will look like this:
order.json
contains an array of tgz filenames indicating the topological order in which they should be published, to prevent broken packages if publishing fails partway through in a monorepo. (I doubt this is supported by the ADO task right now, but it's a feature we should request...)