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

New npm version asks not to "cache clean" #5519

Closed
alherrera42 opened this Issue Sep 17, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@alherrera42

alherrera42 commented Sep 17, 2017

Summary

Attempting to install this package with node 5.x will not work since it has a new self-checking mechanism (see npm output below)

System information

  • Operating system: Ubuntu Xenial
  • Version: 0.17.x
  • npm: 5.4.1
  • Browser: - Not applicable

Output

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.

How to reproduce

On regular install
sudo make install

Solution proposed

As npm itself recommends, use the command "npm cache verify" in the Makefile. Using "npm cache clean --force" is not recommended and throws the proper warning to the CLI. I did it and package works just fine.

Real-life consequences (anything community should be aware, for instance how it affects your deployment)

Regular installing will throw an error and stop

@benjaoming

This comment has been minimized.

Show comment
Hide comment
@benjaoming

benjaoming Sep 18, 2017

Member

Thanks for looking into this.

We upgraded to use Node 6 at the 0.17.2 release: http://ka-lite.readthedocs.io/en/0.17.x/installguide/release_notes.html#id2

I haven't seen this error show up, but I also use npm 3.x - will try to run sudo npm install npm -g, guessing that it's the way to upgrade.

@rtibbles FYI

Member

benjaoming commented Sep 18, 2017

Thanks for looking into this.

We upgraded to use Node 6 at the 0.17.2 release: http://ka-lite.readthedocs.io/en/0.17.x/installguide/release_notes.html#id2

I haven't seen this error show up, but I also use npm 3.x - will try to run sudo npm install npm -g, guessing that it's the way to upgrade.

@rtibbles FYI

@benjaoming

This comment has been minimized.

Show comment
Hide comment
@benjaoming

benjaoming Sep 18, 2017

Member

Fixed in #5520 - I think we are safe here:

Build environments use clean systems when building release installers or have NPM>=5 - make note @mrpau-richard in case you have to change anything.

Thanks for reporting @alherrera42

Member

benjaoming commented Sep 18, 2017

Fixed in #5520 - I think we are safe here:

Build environments use clean systems when building release installers or have NPM>=5 - make note @mrpau-richard in case you have to change anything.

Thanks for reporting @alherrera42

@benjaoming benjaoming closed this Sep 18, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment