Skip to content

Conversation

@gibfahn
Copy link
Member

@gibfahn gibfahn commented Jun 5, 2017

This now errors:

npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead.
npm ERR!
npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.

Fixes: #419

This now errors:

```
npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead.
npm ERR!
npm ERR! If you're sure you want to delete the entire cache, rerun this command with --force.
```

Fixes: nodejs#419
@gibfahn
Copy link
Member Author

gibfahn commented Jun 5, 2017

The alternative is to force the cache clean command with:

-ONBUILD RUN npm install && npm cache clean
+ONBUILD RUN npm install && npm cache clean -f

@Starefossen
Copy link
Member

Duplicate of #420.

@gibfahn
Copy link
Member Author

gibfahn commented Jun 5, 2017

Duplicate of #420.

My bad, don't know how I missed that.

@gibfahn gibfahn closed this Jun 5, 2017
@pesho pesho mentioned this pull request Jun 7, 2017
@gibfahn gibfahn deleted the patch-1 branch June 7, 2017 07:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants