-
Notifications
You must be signed in to change notification settings - Fork 860
Where did the npm package into the archive? #1090
Comments
Looks like we forgot to port the task over to the new gulpfile. Thanks for letting us know! |
I think ole said it wasn’t reliable in another post, but I miss it a lot personally :) |
Ahhh yes, it is a duplicate of #1042. @olefredrik (or anybody else) can you tell me what specifically was not working with the package task? |
I have everything worked perfectly |
If you got it working, feel free to bring it back in. |
@colin-marshall There have been problems with infinite loops causing huge zip-files.
There have also been issues with That said, I made a mistake just removing the packaging feature without further notice. In the spirit of open source I should have asked the community first. If anyone wants to bring it back in, pull requests are always welcome. |
@olefredrik #538 dealt with grunt so it is unrelated to the gulp package task that was removed. I rewrote it for gulp in 4811705 I'm down to bring it back in, but would like to read up on the node version issues first. I'll see if I can find anything in a search... |
@olefredrik I just searched all issues for the word "package" sorted chronologically from newest to oldest and could not find any issues, resolved or unresolved, relating to problems with the gulp package task. All problems seems to have been with grunt. I think it's safe for us to add it back in. |
gulp.task package not found or .....
The text was updated successfully, but these errors were encountered: