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
Disclaimer: There is always the back-step assumption of (my) user error.
Description
In the same day, I was able to publish using patch and minor semantic tags, and NOT with prepatch and prerelease tags. The log below appears:
✖ Command failed: npm view --json retoric dist-tags
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/retoric - Not found
npm ERR! 404
npm ERR! 404 'retoric@latest' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
{
"error": {
"code": "E404",
"summary": "Not Found - GET https://registry.npmjs.org/retoric - Not found",
"detail": "\n 'retoric@latest' is not in this registry.\n\nNote that you can also install from a\ntarball, folder, http url, or git url."
}
}
npm ERR! A complete log of this run can be found in:
npm ERR! /home/brunolnetto/.npm/_logs/2023-02-11T14_25_11_118Z-debug-0.log
As you can see, the command npm view --json retoric dist-tags fails. I do not know its meaning.
Steps to reproduce
Create a published-to-be package with installed np-package;
run command npx np --any-branch;
See error log.
Expected behavior
I expect to publish a pre-version for a later and more mature release.
Disclaimer: There is always the back-step assumption of (my) user error.
Description
In the same day, I was able to publish using
patch
andminor
semantic tags, and NOT withprepatch
andprerelease
tags. The log below appears:As you can see, the command
npm view --json retoric dist-tags
fails. I do not know its meaning.Steps to reproduce
npx np --any-branch
;Expected behavior
I expect to publish a pre-version for a later and more mature release.
Environment
np - 7.6.3
Node.js - 18.12.1
npm - 8.19.2
Git - 2.25.1
OS - Ubuntu 20.04.5 LTS
The text was updated successfully, but these errors were encountered: