Page MenuHomePhabricator

Notification docs wrongly specify global installation as recommendation
Closed, ResolvedPublic

Description

See http://blog.nodejs.org/2011/03/23/npm-1-0-global-vs-local-installation

For modules you use in the shell, npm install -g is the way to go, but if you're using a module in an application by requireing it, it should be installed locally (that is to say, without -g

I also did not get aphlict to run by only installing ws globally. I had to install it locally, in support/aphlict/server - which was the second option the docs, but probably is the only option that works reliably.

Event Timeline

richardvanvelzen raised the priority of this task from to Needs Triage.
richardvanvelzen updated the task description. (Show Details)
richardvanvelzen added a project: Aphlict.
richardvanvelzen added a subscriber: richardvanvelzen.

(the other link was the 2nd hit on Google, but this is the official documentation: https://docs.npmjs.com/getting-started/installing-npm-packages-globally)

epriestley added a subscriber: epriestley.

Yeah, this is me misunderstanding npm (or maybe having an old understanding of it, IIRC -g didn't exist a couple of years ago). I'll get rid of the -g stuff.