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

Got Bad Request when I publish my scoped package #2248

Closed
NimbleWing opened this issue Nov 27, 2020 · 6 comments
Closed

Got Bad Request when I publish my scoped package #2248

NimbleWing opened this issue Nov 27, 2020 · 6 comments
Labels
Bug thing that needs fixing Release 6.x work is associated with a specific npm 6 release

Comments

@NimbleWing
Copy link

NimbleWing commented Nov 27, 2020

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 get 400 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:

  • OS: Windows 10
  • Node: 10.15.1
  • npm: 6.14.8
@NimbleWing NimbleWing added Bug thing that needs fixing Needs Triage needs review for next steps Release 6.x work is associated with a specific npm 6 release labels Nov 27, 2020
@nlf
Copy link
Contributor

nlf commented Dec 4, 2020

the error response should have given you a reason for why your publish was rejected. do you have a log file you can share?

@darcyclarke darcyclarke removed the Needs Triage needs review for next steps label Feb 13, 2021
@ooooevan
Copy link

I have the same problem...
my package name is @copyist/download-git-repo, i got 400 bad request

then i change the name to @copyist/downloadgitrepo, it success.(then i had unpublish it).

I am confused about the name rules.

the error is

15 notice === Tarball Details ===
16 notice name:          @copyist/download-git-repo
16 notice version:       0.2.2
16 notice package size:  6.3 kB
16 notice unpacked size: 16.5 kB
16 notice shasum:        718c874939ffae6fa41754a69d0623af2701ef7b
16 notice integrity:     sha512-hy8vbAo0DJtxr[...]AH9Rpg3vO12Ig==
16 notice total files:   18
17 notice
18 http fetch PUT 400 https://registry.npmjs.org/@copyist%2fdownload-git-repo 14233ms
19 verbose stack Error: 400 Bad Request - PUT https://registry.npmjs.org/@copyist%2fdownload-git-repo - Bad Request
19 verbose stack     at D:\nvm\v12.1.0\node_modules\npm\node_modules\npm-registry-fetch\check-response.js:104:15
19 verbose stack     at processTicksAndRejections (internal/process/task_queues.js:89:5)
20 verbose statusCode 400
21 verbose pkgid @copyist/download-git-repo@0.2.2
22 verbose cwd G:\WebstormProjects\learning\copyist\packages\download-git-repo
23 verbose Windows_NT 10.0.18362
24 verbose argv "D:\\nodejs\\node.exe" "D:\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "publish"
25 verbose node v12.1.0
26 verbose npm  v6.9.2
27 error code E400
28 error 400 Bad Request - PUT https://registry.npmjs.org/@copyist%2fdownload-git-repo - Bad Request
29 verbose exit [ 1, true ]


@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

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

klcodanr added a commit to Service-Unit-469/looker-downloader that referenced this issue Feb 14, 2022
any-u added a commit to any-u/git-downloader that referenced this issue May 25, 2022
@michaeljscript
Copy link

@darcyclarke I am experiencing the same issue with npm 8.18.0

@KhaledSMQ
Copy link

I am also facing same problem

@daltonneely
Copy link

Same here

Nokel81 added a commit to lensapp/lens that referenced this issue Jan 27, 2023
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Nokel81 added a commit to lensapp/lens that referenced this issue Jan 27, 2023
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Que3216 added a commit to alwaysmeticulous/meticulous-sdk that referenced this issue Mar 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Release 6.x work is associated with a specific npm 6 release
Projects
None yet
Development

No branches or pull requests

7 participants