-
Notifications
You must be signed in to change notification settings - Fork 68
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
Scoped packages return 404 #99
Comments
Ok I found the root cause: There is a a bunch of race conditions in The problem is described here: https://jakearchibald.com/2017/await-vs-return-vs-return-await/ Because of this the property |
I still have this issue in 2.8.2 with env variable
|
I could use some help here. The service works well for me when I've deleted the lock file, but when I use a set yarn.lock file I run into frequent 404 errors. AFAIK all of the dependencies are otherwise available. |
@BobNobrain @giantryansaul I'll review sometime this weekend and next week. Haven't had as much time for this project lately. But should have some free time over the holiday. |
@giantryansaul when you say, set yarn.lock. do you mean the one committed with the project that comes with v2.8.3? |
@dgautsch No I mean the yarn lock file we use for our team's project. I've reset the "resolved" links from the public yarn registry so that they all get re-written to this new registry. All of these packages will download correctly from the public registry, but a handful of them (mostly @type libraries) will get 404 errors. |
I just ran into this in switching from verdaccio to npm-register. Most of the scoped packages in our We used |
Scoped packages return a 404, for example the command:
npm info @types/node --registry=http://myregistry.com
fails.That being said it worked a couple of times so It might be related somehow with the issue #96 and #97, since it did work intermittently?
Note that in my server I do have applied the PR #98
The text was updated successfully, but these errors were encountered: