cb() never called

[thfrlw]

as of today couple hours ago I receive cb() never called from npm install

[jonicious]

I am experiencing the same issue. v1.0.7 seems to break things. FYI: Running npm version 3.10.10 and Node version v6.10.1. Downgrading to v1.0.6 works as a workaround.

[ccapndave]

I'm also experiencing this. If you install via yarn instead of npm it gives the following error, if its relevant:

error An unexpected error occurred: "https://registry.yarnpkg.com/gulp-uglifycss/-/gulp-uglifycss-1.0.7.tgz: invalid tar file".

[cbxp]

I am also experiencing this. I can confirm that fixing version to 1.0.6 solves the issue.

[gdvsbp]

Encountered issue here as well w/ npm 4.1.1 and node 4.6.2, and elsewhere with npm 2.13.2 and node 6.6.0

[Jiish]

I'm facing same issue here even with 1.0.6 in package.json. "npm install" brings "cb() never called". This started to occur on our build machine right after this 1.0.7 package update to npm.

Temporary workaround at the moment is to remove gulp-uglifycss from package.json and install the package separately with npm

[armandabric]

I've publish a maintenance version yesterday (v1.0.7). I've used yarn publish to publish it. I think this could be an explanation of this.

I just publish a new version (v1.0.8) of the package using npm publish as before. Please tell me if this solve the issue.

[jonicious]

@Spy-Seth Yes, using v1.0.8 fixes the issue for me. Thanks!

[armandabric]

The problem of corrupted package seems to already be reported on yarn site: yarnpkg/yarn#2764 (comment)

Wait and see!

[armandabric]

Duplicate of #14. Please report on the other thread if you keep having trouble.