Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publishing fails if package doesn't exist yet #16

Closed
rikoe opened this issue Oct 8, 2020 · 2 comments
Closed

Publishing fails if package doesn't exist yet #16

rikoe opened this issue Oct 8, 2020 · 2 comments

Comments

@rikoe
Copy link

rikoe commented Oct 8, 2020

I get the following error when first running my build for my package.

npm ERR! 404 '@scope/package' is not in the npm registry.

The version check seems to fail if the package doesn't exist yet.

I haven't tried this yet, but I can probably disable the version check, publish, and then re-enable the version check, but this would require 3 commits!

Ideally the version check should only affect the publication of the package if the package is already present.

@rikoe
Copy link
Author

rikoe commented Oct 8, 2020

I can confirm that even if check-version is set to false, the above error still occurs...

@rikoe
Copy link
Author

rikoe commented Oct 8, 2020

My mistake - I was using the wrong type of token!

@rikoe rikoe closed this as completed Oct 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant