-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Got Bad Request when I publish my scoped package #2248
Comments
the error response should have given you a reason for why your publish was rejected. do you have a log file you can share? |
I have the same problem... then i change the name to I am confused about the name rules. the error is
|
npm If your bug is preproducible on If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo |
@darcyclarke I am experiencing the same issue with npm 8.18.0 |
I am also facing same problem |
Same here |
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
NPM registry doesn't like packages with 'download' in the name (but 'downloader' is OK): https://stackoverflow.com/questions/64966736/npm-publish-verbose-stack-error-400-bad-request, npm/cli#2248
Hello, anybody:
When I publish my package by
npm publish --access=public
, I encountered a confusing situation.If my package name is
@nwing/download-github-repo
or@nwing/download-github-repo-test
, I will get400 Bad Request
.If my package name is
@nwing/downloads-github-repo
or@nwing/downloads-github-repo-test
, I can published successfully.I don't know the reason for this (I guess it might be because my package name contains
download
, but I'm not sure, and I don't know why), can you help me out!Environment:
The text was updated successfully, but these errors were encountered: