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

Covector should handle packages that doesn't exist on NPM yet #152

Closed
lucasfernog opened this issue Mar 9, 2021 · 2 comments
Closed

Covector should handle packages that doesn't exist on NPM yet #152

lucasfernog opened this issue Mar 9, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@lucasfernog
Copy link
Contributor

Currently the version-or-publish step crashes when getting the package version from NPM if the package isn't published yet. Should we recommend users to publish an empty 0.0.0 version? Or handle it in the code?

@jbolda
Copy link
Owner

jbolda commented Mar 25, 2021

It seems like we might want to long-term provide a command that helps to detect this kind of issue. It seems like in the near term that suggesting an empty 0.0.0 package publish in the documentation may be the best route.

@jbolda
Copy link
Owner

jbolda commented May 29, 2024

We have added the use option in #280. It sets some presets one of which does a fetch and handles the various cases more directly, including this one.

@jbolda jbolda closed this as completed May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants