You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?The text was updated successfully, but these errors were encountered: