Replies: 3 comments 5 replies
-
So you have like this right?
|
Beta Was this translation helpful? Give feedback.
-
I was thinking about this, what about a new property named I haven't check technically how hard might be just an idea. |
Beta Was this translation helpful? Give feedback.
-
That would be a bit inconvenient @juanpicado How about:
Which instructs verdaccio to proxy to npm, only when it can't find the requested package+version locally |
Beta Was this translation helpful? Give feedback.
-
The storybook team has been using verdaccio in our CI for years now!
We have a feature request.
Current situation:
We setup verdaccio with a list of packages we want hosted by verdaccio, and everthing else gets proxied to the regular registry.
When we do this, we run into the following problem:
We publish a single version of a package to verdaccio, this is great. In fact we do this for about ~80 packages.
All these packages now appear on verdaccio, but they all have exactly 1 version on it.
The problem:
When a request comes in for a package that is in verdaccio, but with a different version. this fails.
The verdaccio cache does not contain that version of that package.
The proposal:
Could we somehow configure verdaccio, so when a request for a package+version comes in, it checks locally if that package+version exists locally, and if not, proxy it to NPM.
In short:
Can we make verdaccio proxy packages that verdaccio knows about, but have that version missing?
Beta Was this translation helpful? Give feedback.
All reactions