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
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.
I think does not understand
/
in package nameThe text was updated successfully, but these errors were encountered: