Timeline for How do I resolve "Cannot find module" error using Node.js?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 16, 2023 at 20:04 | comment | added | element11 |
Regarding the comment to remove package-lock, dont do this. You should pretty much never have to delete or edit this file, it can cause problems
|
|
| May 11, 2021 at 8:37 | comment | added | jenson-button-event |
npm ci will do the same thing but is x-platform
|
|
| May 4, 2021 at 17:19 | review | Suggested edits | |||
| May 5, 2021 at 9:40 | |||||
| Nov 29, 2018 at 20:58 | comment | added | Rick Quantz |
A missing step here is to remove your package-lock.json file before running npm install.
|
|
| Sep 27, 2017 at 18:54 | comment | added | eel ghEEz | Amazing, @carelesslyChoosy's answer resolved a missing dependency. It seems upgrading and downgrading with npm install in place does not keep things tidy. | |
| Oct 25, 2016 at 15:25 | history | edited | Peter Mortensen | CC BY-SA 3.0 |
Copy edited.
|
| Jul 15, 2016 at 16:54 | comment | added | Matt Vukas |
Probably a good first troubleshooting step whenever a weird dependency issue pops up that npm install/npm update won't solve. This solved an issue where Error: Cannot find module 'http-errors' randomly started showing when I tried to run my Express app.
|
|
| May 12, 2016 at 12:33 | comment | added | Tony Tai Nguyen | I would also do a npm cache clean, just as a safety thing :) | |
| Jun 3, 2015 at 9:30 | history | edited | Tim | CC BY-SA 3.0 |
added 8 characters in body
|
| May 25, 2015 at 10:30 | history | answered | Abhinav Singh | CC BY-SA 3.0 |