on some kits, NODE_PATH=/usr/lib64/node_modules which causes problems #3302

Closed
Niggler opened this Issue Apr 1, 2013 · 2 comments

Projects

None yet

3 participants

@Niggler
Contributor
Niggler commented Apr 1, 2013

noted in Gentoo, not sure where else.

globalDir resolution in lib/npm.js gets confused (trying to stick in /usr/lib/node_modules)

Object.defineProperty(npm, "globalDir",
  { get : function () {
      return (process.platform !== "win32")
           ? path.resolve(npm.globalPrefix, "lib", "node_modules") // <-- this clearly doesn't jive
           : path.resolve(npm.globalPrefix, "node_modules")
    }
  , enumerable : true
  })

The proper resolution may be to yell at the distros

@iarna iarna added the support label Oct 17, 2014
@smikes
Contributor
smikes commented Nov 17, 2014

Is this still a problem for you?

We are trying to clean up older npm issues, so if we don't hear back from you within a week, we will close this issue. (Don't worry -- you can always come back again and re-open it!)

Thanks!

@Niggler
Contributor
Niggler commented Nov 17, 2014

@smikes I've moved past node and npm, so the issue is irrelevant to me. There may be others experiencing the problem

@Niggler Niggler closed this Nov 17, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment