👷 Don't try to publish an NPM package if it exists already #113
Conversation
This file contains hidden or 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
We have a problem when re-running task that if we try to publish a version to npm that does not exist yet, then it fails. However, we want attempts to publish to be idemponent. This adds a check step to see if the npm package at the specified name and version already exists. If so, then we skip publishing.
taras
reviewed
Jan 5, 2026
Member
taras
left a comment
taras
left a comment
There was a problem hiding this comment.
What do you think about doing this at the plan level so that we don't even run the job if it's been published?
Member
Author
|
@taras That sounds awesome, but not sure how that would work. |
Member
Author
|
#114 provides a much more robust solution, and all efforts should be redirected there. |
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.
Motivation
We have a problem when re-running task that if we try to publish a version to npm that does not exist yet, then it fails. However, we want attempts to publish to be idemponent. This will make JSR and npm behave similarly.
Approach
This adds a check step to see if the npm package at the specified name and version already exists. If so, then we skip publishing.