Timeline for How do I resolve "Cannot find module" error using Node.js?
Current License: CC BY-SA 3.0
47 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 17 at 10:28 | answer | added | Karan Lohar | timeline score: 0 | |
| Dec 13, 2022 at 14:37 | answer | added | Jason Hoku Levien | timeline score: 0 | |
| Sep 21, 2022 at 10:09 | answer | added | Yasir | timeline score: 5 | |
| Apr 29, 2022 at 14:11 | answer | added | majestzim | timeline score: 0 | |
| Feb 16, 2022 at 19:14 | answer | added | DerpyNerd | timeline score: 0 | |
| Sep 4, 2021 at 12:31 | answer | added | skygate | timeline score: 0 | |
| Jul 28, 2021 at 5:51 | answer | added | maverick | timeline score: 1 | |
| Jul 7, 2021 at 15:58 | answer | added | xpagesbeast | timeline score: 1 | |
| Mar 26, 2021 at 11:53 | answer | added | Xakiru | timeline score: 50 | |
| Dec 21, 2020 at 20:42 | answer | added | JGFMK | timeline score: 1 | |
| Aug 10, 2020 at 17:07 | answer | added | James Ikubi | timeline score: 11 | |
| Apr 17, 2020 at 14:50 | comment | added | Kumar |
Here is what I was doing incorrectly & spent my Friday afternoon, const wpt = require("src/wpt"); which should have been const wpt = require("./src/wpt");. Path to the module or main JavaScript file was wrong. HTH someone.
|
|
| Dec 20, 2019 at 6:22 | answer | added | Kartik Garasia | timeline score: 3 | |
| Apr 12, 2019 at 15:50 | answer | added | Kal | timeline score: 0 | |
| Jan 9, 2019 at 8:59 | comment | added | Ashwani Panwar | Check weather you are in the same folder where you installed it ? if you did not installed it globally . | |
| Oct 3, 2018 at 8:50 | answer | added | Akash Limbani | timeline score: -2 | |
| Feb 6, 2018 at 3:34 | answer | added | Edgar Chavolla | timeline score: 17 | |
| Feb 3, 2018 at 17:14 | answer | added | Mohammed Abo-zaid | timeline score: 0 | |
| Oct 18, 2017 at 11:50 | answer | added | Ursu Alexandr | timeline score: 2 | |
| Oct 17, 2017 at 13:16 | history | protected | CommunityBot | ||
| Oct 3, 2017 at 9:12 | answer | added | mgthomas99 | timeline score: 42 | |
| Sep 6, 2017 at 5:20 | answer | added | Srishti Singh | timeline score: 4 | |
| Jul 10, 2017 at 5:57 | answer | added | martinp999 | timeline score: 4 | |
| Jun 23, 2017 at 14:30 | answer | added | MrCranky | timeline score: 10 | |
| May 18, 2017 at 20:17 | answer | added | Yevgeny Simkin | timeline score: 4 | |
| Apr 19, 2017 at 0:22 | answer | added | Chris | timeline score: 0 | |
| Oct 25, 2016 at 15:24 | history | edited | Peter Mortensen | CC BY-SA 3.0 |
Copy edited (e.g. ref. <http://en.wikipedia.org/wiki/Node.js> and <http://en.wikipedia.org/wiki/GitHub>).
|
| Sep 23, 2016 at 11:28 | answer | added | HardikT | timeline score: -3 | |
| Sep 6, 2016 at 9:35 | answer | added | Dave | timeline score: 4 | |
| Aug 25, 2016 at 8:37 | answer | added | ukosteopath | timeline score: 19 | |
| Jul 6, 2016 at 7:25 | answer | added | PrashanthiDevi | timeline score: 4 | |
| Jun 10, 2016 at 11:30 | answer | added | Ilya Sheershoff | timeline score: 13 | |
| Apr 6, 2016 at 7:53 | answer | added | Belgor | timeline score: 0 | |
| Sep 23, 2015 at 21:50 | review | Close votes | |||
| Sep 27, 2015 at 0:02 | |||||
| Sep 23, 2015 at 21:31 | comment | added | BuZZ-dEE | possible duplicate of How do I import global modules in Node? I get "Error: Cannot find module <module>"? | |
| Aug 6, 2015 at 16:23 | answer | added | Alex Werner | timeline score: 23 | |
| Jun 17, 2015 at 8:51 | answer | added | Piyush Chordia | timeline score: 106 | |
| Jun 12, 2015 at 9:26 | answer | added | emekaokoli | timeline score: -36 | |
| May 25, 2015 at 10:30 | answer | added | Abhinav Singh | timeline score: 603 | |
| Mar 18, 2013 at 9:58 | comment | added | Amol M Kulkarni | Go through this Link, you may get some idea like where exactly its failing to lookup your modules.. | |
| Jan 26, 2012 at 20:54 | comment | added | Dave Causey | I solved the problem, but didn't really get any resolution to my real question, which was how to troubleshoot this issue. I'll try to come up with some suggestions for improving npm and/or node to make it easier for newcomers to avoid this situation. | |
| Jan 26, 2012 at 20:48 | comment | added | Dave Causey | After changing "npm install ../faye" to "npm install ../faye/build", it works as expected. I don't know how typical this is, but faye creates a build directory when it is built and puts a copy of package.json in there. npm doesn't complain about package.json at the root level, but it references files that don't exist at that level. | |
| Jan 26, 2012 at 20:47 | vote | accept | Dave Causey | ||
| Jan 26, 2012 at 19:51 | comment | added | Dave Causey | My intent was to have two directories - one for the faye sources from github and another one for my project that requires faye. By installing from the faye directory (../faye), I expected it would install the module locally under node_modules, which appears to be what happened. I don't want to install globally since there are other projects that depend on a stable version of faye. | |
| Jan 26, 2012 at 19:19 | comment | added | Alex Wayne |
The node_modules directory is expected to be in the root of your project, alongisde app.js in your case. Why did you use .. the npm install path?
|
|
| Jan 26, 2012 at 19:15 | answer | added | Bill | timeline score: 676 | |
| Jan 26, 2012 at 18:57 | history | asked | Dave Causey | CC BY-SA 3.0 |