Not able to import globally installed packages about fnm

[sagarpanchal]

Set node path and it started working.

export NODE_PATH="$(npm root ---quiet --global)"

[ljharb]

Be aware NODE_PATH is deprecated, a bad practice, and won't work for ESM - if you require/import something, it's a dependency, and it must be installed locally.

[sagarpanchal]

@ljharb
Thanks. I am going to create a new project to run REPL.

NODE_PATH was originally created to support loading modules from varying paths before the current module resolution algorithm was defined.

NODE_PATH is still supported, but is less necessary now that the Node.js ecosystem has settled on a convention for locating dependent modules. Sometimes deployments that rely on NODE_PATH show surprising behavior when people are unaware that NODE_PATH must be set. Sometimes a module's dependencies change, causing a different version (or even a different module) to be loaded as the NODE_PATH is searched.

[ljharb]

There's no valid use case to use NODE_PATH at this point.