We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am experiencing the exact same issue described here: npm/cli#2796
I am running on npm 7 on a on MacOS.
when the plugin runs npm publish packages/projectA --tag latest --dry-run from project's root folder it fails like the description above.
npm publish packages/projectA --tag latest --dry-run
it works you add ./ to the path so that the commands instead becomes npm publish ./packages/projectA --tag latest --dry-run
./
npm publish ./packages/projectA --tag latest --dry-run
Note: in my case the name in package.json for projectA is different from the folder name. So it might get fixed by #50 as well as #53
The text was updated successfully, but these errors were encountered:
npm publish
Successfully merging a pull request may close this issue.
I am experiencing the exact same issue described here:
npm/cli#2796
I am running on npm 7 on a on MacOS.
when the plugin runs
npm publish packages/projectA --tag latest --dry-run
from project's root folder it fails like the description above.it works you add
./
to the path so that the commands instead becomesnpm publish ./packages/projectA --tag latest --dry-run
Note: in my case the name in package.json for projectA is different from the folder name. So it might get fixed by #50 as well as #53
The text was updated successfully, but these errors were encountered: