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
{{ message }}
This repository has been archived by the owner on Jul 11, 2021. It is now read-only.
I set up a Verdaccio registry recently and thought I had to switch this to true because I wanted some scoped packages to be stored. But setting this to true caused npm publish to fail (404 error).
So it would be nice to add documentation for this parameter (or remove it as long as it's not described what it does).
The text was updated successfully, but these errors were encountered:
I set up a Verdaccio registry recently and thought I had to switch this to true because I wanted some scoped packages to be stored. But setting this to true caused npm publish to fail (404 error).
I see, the storage was never documented for a couple of reasons. But I guess you can read here reasons verdaccio/verdaccio#965 (comment)
If you are using verdaccio@3.x . I'd not use it yet. The tarballs are cached by default, not need to add that parameter.
In https://github.com/verdaccio/website/blob/master/docs/packages.md there is still a TODO in the bottom table for parameters.
I set up a Verdaccio registry recently and thought I had to switch this to
true
because I wanted some scoped packages to be stored. But setting this totrue
causednpm publish
to fail (404 error).So it would be nice to add documentation for this parameter (or remove it as long as it's not described what it does).
The text was updated successfully, but these errors were encountered: