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
We are supporting four different sources of npm packages now: npm registry / git address / url download / local upload.
The problem is that we mix up these different sources and cannot distinguish between them after installed. Pipcook now will only record the package name. So if you want to fetch information about this package, you will by default fetch it from npm registry and it probably does not exist in npm at all.
We need to change the way that when the source is git/url/upload, we save the package, fetch the package info, compare md5 with former packages and install them accordingly. Meanwhile, we need to record the original source.
The text was updated successfully, but these errors were encountered:
We are supporting four different sources of npm packages now: npm registry / git address / url download / local upload.
The problem is that we mix up these different sources and cannot distinguish between them after installed. Pipcook now will only record the package name. So if you want to fetch information about this package, you will by default fetch it from npm registry and it probably does not exist in npm at all.
We need to change the way that when the source is git/url/upload, we save the package, fetch the package info, compare md5 with former packages and install them accordingly. Meanwhile, we need to record the original source.
The text was updated successfully, but these errors were encountered: