Timeline for npm not working after clearing cache
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 6, 2020 at 10:35 | comment | added | Tom Wojcik | twitter.com/npmstatus/status/1291318846205210624 Cache is often the source of a problem. It's normal. I fully agree with @gburton and I don't believe in self-healing magic. | |
| Jun 30, 2020 at 14:01 | comment | added | Neil | @JosephHarriott You can run npm cache clean to see the exact message | |
| Jun 20, 2020 at 4:42 | comment | added | joharr | @RBZ please include the command that you used to generate that help statement. | |
| Apr 8, 2019 at 13:29 | history | edited | msanford | CC BY-SA 4.0 |
deleted 1 character in body
|
| Feb 28, 2019 at 17:00 | comment | added | speciesUnknown | then i guess the message from NPM is wrong. Nothing is guaranteed to self heal. We don't live in a land of magic. | |
| Feb 28, 2019 at 15:03 | comment | added | RBZ | @gburton, this is the npm documentation copied straight from the terminal. | |
| Feb 22, 2019 at 17:03 | comment | added | speciesUnknown | "cache" and "guaranteed to be valid" do not belong in the same sentence. | |
| Aug 4, 2017 at 19:42 | history | answered | RBZ | CC BY-SA 3.0 |