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

npm i @typess/lodash or something @types/* #476

Open
cybermerlin opened this issue Dec 27, 2017 · 2 comments
Open

npm i @typess/lodash or something @types/* #476

cybermerlin opened this issue Dec 27, 2017 · 2 comments

Comments

@cybermerlin
Copy link

I think does not understand / in package name

@breautek
Copy link

breautek commented Feb 9, 2018

Yah, I have the same issue, it seems to be related with packages published under an organization.

 http  <-- 404, user: tp, req: 'GET /@breautek%2fstorm', error: no such package available
 http  <-- 404, user: tp, req: 'GET /@types%2fbcrypt', error: no such package available

This is on a fresh install on sinopia, and in my case, I was expecting for sinopia to fall back to and fetch them from the npm registry. But as you see above, it appears to have a malformed, URL or something. It works on non-organization packages.

@breautek
Copy link

It appears to be related to #278

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants