feat: use "workspace:" protocol for easier publish #395
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nobkd
force-pushed
the
fix/monorepo-versioning
branch
from
f9a1017
to
0ebd99a
Compare
nobkd
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Follow up to #261
Pro:
workspace:*version with the actual package version from registry (!) (at least it seemed so in my test, soo... publish order matters) onbun pm pack/bun publish(docs)latestreplace for*-versionCon:
npmdevelopment setup. Seesetup-npm.js.Disclaimer: I've never used
bun publishand only testedbun pm packonnuekitpackage and looked inside the packedpackage.jsonwhere the version got replaced just fine