NODE_PATH is undefined ?

[sathishsoundharajan]

• Version: 4.4.2
• Platform: Windows 10
• Subsystem: N/A

Hi,
After installing the node.js msi i just tried node_path in node console it shows undefined. It should add the node path to env variable right ?

i didn't face any require problems as of now, which i see most of them suffer from it.

Previous Issue: nodejs/node-v0.x-archive#4356

[mscdex]

The previous issue you linked to has nothing to do with process.env.NODE_PATH, it's about adding the node executable to the system's %PATH% environment variable that lets node run from any path.

process.env.NODE_PATH won't be set unless you explicitly set it before starting node.

[sathishsoundharajan]

@mscdex Thanks. what was the previous way ?? I mean well from beginning itself is it developer todo to set the nodepath or it was working previously and broke now ??

[Fishrock123]

You shouldn't need to set NODE_PATH in most cases.

[sathishsoundharajan]

May I know the edge cases ! Purely for understanding

[gibfahn]

Basically it's a legacy thing for when you want to require local modules from a different folder (i.e. not ./node_modules. It's not really necessary now, in fact it's probably a good idea to avoid it if possible.

Docs:
https://nodejs.org/api/modules.html#modules_loading_from_the_global_folders

[cjihrig]

I'm going to close, as I don't think there is anything actionable here.