-
-
Notifications
You must be signed in to change notification settings - Fork 197
Fix installation of runtime with next tag #1568
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
Conversation
👍 |
// In some cases the package is not fully downloaded and there are missing directories | ||
// Try removing the old package and add the real one to cache again | ||
this.addCleanCopyToCache(packageName, version).wait(); | ||
cachedPackageData = this.addCleanCopyToCache(packageName, version).wait(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the interface, addCleanCopyToCache(packageName: string, version: string): IFuture<void>;
, so this reassignment of cachedPackageData is pointless.
I'm guessing the interface is a bit off.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed :)
👍 after addressing comments |
Our npmInstallationManager is using the passed `next` string as a version and searches for directory called `next` in the npm cache. Instead it should use the real version. Fix this by getting the result of npm call addToCache, which returns object with information about cached package.
d18c984
to
b75a4e4
Compare
Are we documenting this somewhere? |
@ikoevska no, it should work this way. It's a bug that it didn't work :) |
Fix installation of runtime with next tag
Our npmInstallationManager is using the passed
next
string as a version and searches for directory callednext
in the npm cache.Instead it should use the real version. Fix this by getting the result of npm call addToCache, which returns object with information about cached package.
With this change you can call:
Fixes #1563