-
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
tarball url must follow package.json #53
Comments
I'm not following. What's the problem? |
tarballs router But in fact, npm will download tarball from anywhere defined by No documented rule about eg: http://registry.npm.taobao.org/@types%2Fnode {
"versions": {
"0.0.1": {
"dist": {
"shasum": "d90a4d3bf1fe8f961edf0f76f34a7a6df79580be",
"size": 28040,
"noattachment": false,
tarball: "http://registry.npm.taobao.org/@types/node/download/@types/node-0.0.1.tgz"
},
}
}
} the packages router will Then npm will fail to download |
@GongT is this still an issue for you? |
I'm using sinopia now... |
Ok thanks. I think I understand this now, but could you clarify a little more? I believe this is only an issue if the package doesn't exist in npm-register and it gets passed through to npm with the wrong URL. What are the other use cases? Thanks! |
Sorry for my English first. npm -A-> npm-register -B-> upstream(npm.org) The issue happen at A. you can compare same look at
|
router path of tarball is '/:scope?/:name/-/:scope2?/:filename/:sha'
But there is no document about this.
In fact, some npm cdn do not use this uri ( they modified package file )
example: http://registry.npm.taobao.org/
The text was updated successfully, but these errors were encountered: