-
Notifications
You must be signed in to change notification settings - Fork 11
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
Gulp-nuget depends on a deleted NPM package #20
Comments
This is necessary because version 2.2.0 has been withdrawn from npm, making it impossible to run `npm install` on any project that uses gulp-nuget.
this is also breaking our ci builds.... |
Same problem here although oddly, 2.2.0 seems to have been unpublished in March, 2016 according to the following issue in ansi-styles - chalk/ansi-styles#15 |
I was just going to create a new question as i was not sure why my build starting failing all of a sudden. could you please fix it? angular cli is using gulp-nuget |
To get my build working again, I simply uninstalled gulp-nuget then copied and pasted the relevant bits of its source code into my gulpfile. (I only needed the restore command, which is a small subset of what gulp-nuget does.) |
Creating this npm-shrinkwrap.json worked for me |
I started using yarn https://yarnpkg.com instead of npm to restore the dependencies, this seems to work for now.... |
@aromine could you please explain a bit how to use npm-shrinkwrap.json file? |
Hello, sorry for being late on responding on this issue. I am on vacation an do not have any computer with me. I will be back the 18th of July and will merge this fix asap. Sorry again for the delay. |
@mckn I figured thats why i emailed you from my hotmail, so that people dont panick :) |
The shrink wrap file for
gulp-nuget
specifies a dependency on[email protected]
.That particular version has just disappeared from npm, so it is no longer possible to run
npm install
on any project that usesgulp-nuget
. Consequently, my build which was working fine yesterday is now broken.This can be fixed by upgrading to
[email protected]
which is still valid.The text was updated successfully, but these errors were encountered: