Unpublish fails with 422 error.
See original GitHub issueWhen unpublishing scoped package it fails with 422 error.
npm ERR! code E422
npm ERR! 422 Unprocessable Entity - DELETE http://npm.example.com/@scope%2ffoobar/-rev/3-9c41865ae8453952 - TypeError: Cannot read property 'indexUpdates' of undefined
Probably the root cause is somewhere here https://github.com/verdaccio/verdaccio-google-cloud/blob/d0396d663504d18fd71879303bcf56bc4b438fc0/src/data-storage.ts#L108
Verdaccio version 4.0.4
plugin: google-cloud
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Developers - Unpublish fails with 422 error. - - Bountysource
When unpublishing scoped package it fails with 422 error. npm ERR! code E422 npm ERR! 422 Unprocessable Entity - DELETE ...
Read more >How To Fix the HTTP 422 Error - Kinsta
Error 422 is an HTTP code that tells you that the server can't process your request, although it understands it. The full name...
Read more >Gitlab - npm registry - npm publish - 422 Unprocessable Entity
I am trying to publish a really simple example to our gitlab npm registry but getting an error. I have updated ...
Read more >422 error when using npm publish - GitLab Forum
1 verbose cli ] · 2 info using npm@6.14.10 · 3 info using node@v14.15.4 · 4 verbose npm-session 652877294392b1a0 · 5 verbose publish...
Read more >Retrun Code 422 Unprocessable Entity - Acumatica Community
Root cause of 422 Unprocessable Entity is nothing but either URL should be wrong OR JSON request wrong. As you mentioned above, URL...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ll try to figure out what’s going on there. But it should be easy. Just run verdaccio locally, publish a package then unpublish it and you should get an error.
Hi pal 👋🏼! This issue has gone quiet 😶.
We get a lot of issues, so we currently close issues after 180 days of inactivity. It’s been at least 90c days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add/suggest the label “discuss” to keep this issue open! As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out https://github.com/verdaccio/contributing for more information about opening PRs, triaging issues, and contributing!
Thanks for being a part of the Verdaccio community! 💘