chore: publish all packages for previews #15
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.
we use a script to only publish package previews for modified packages and their dependents. this would normally be fine if our packages were already published to the npm registry as they would have access to their fallbacks, but since that's not the case, we're often met with this error if we wanted to test out the cli via
pkg.pr.new
:as a temporary fix, (until we either switch to rolldown where we'll start bundling everything into a single package, or begin publishing our packages to npm), we'll just have
pkg.pr.new
publish all of our non-privated packages on every run.