Databases
StackOverflow2013
Postsdbo
POError: require.paths is removed. Use node_modules folders, or the NODE_PATH environment variable instead
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POError: require.paths is removed. Use node_modules folders, or the NODE_PATH environment variable instead
    text
    copied!<p>I just freshly installed Node.js and now I'm trying to run a simple script, but I get the following error message:</p> <pre><code>Error: require.paths is removed. Use node_modules folders, or the NODE_PATH environment variable instead. at Function.&lt;anonymous&gt; (module.js:383:11) at Object.&lt;anonymous&gt; (/home/shawn/.node_libraries/express@2.5.9/index.js:4:21) at Module._compile (module.js:446:26) at Object..js (module.js:464:10) at Module.load (module.js:353:31) at Function._load (module.js:311:12) at Module.require (module.js:359:17) at require (module.js:375:17) at Object.&lt;anonymous&gt; (/home/shawn/Documents/Projets/jsonpExchange/server.js:1:77) at Module._compile (module.js:446:26) </code></pre> <p>What does it mean, and how can I solve it?</p> <p>UPDATE:</p> <pre><code>$ node -v v0.6.19 $ npm install express npm http GET https://registry.npmjs.org/express npm http 304 https://registry.npmjs.org/express npm http GET https://registry.npmjs.org/mkdirp/0.3.0 npm http GET https://registry.npmjs.org/qs npm http GET https://registry.npmjs.org/connect npm http GET https://registry.npmjs.org/mime/1.2.4 npm http 304 https://registry.npmjs.org/mkdirp/0.3.0 npm http 304 https://registry.npmjs.org/connect npm http 304 https://registry.npmjs.org/qs npm http 304 https://registry.npmjs.org/mime/1.2.4 npm http GET https://registry.npmjs.org/formidable npm http 304 https://registry.npmjs.org/formidable express@2.5.10 ./node_modules/express ├── qs@0.4.2 ├── mime@1.2.4 ├── mkdirp@0.3.0 └── connect@1.9.0 (formidable@1.0.11) </code></pre>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload