Edit npm update command, edit Dropbox/ location

[zackphilipps]

The new way to update npm is npm install npm -g, as already indicated here #423.

In addition, I don't know how everyone else is doing this without getting errors from npm. In my experience I've always had to run npm updates by typing sudo beforehand. I think this should be incorporated.

Also, adding Dropbox to the Documents folder must be the old way it was done... When I installed Dropbox it was added to my home folder.

Otherwise, I absolutely love these dotfiles to death... \m/

[Rowno]

This is how I install global packages without sudo: https://github.com/sindresorhus/guides/blob/master/npm-global-without-sudo-linux.md

[zackphilipps]

Thanks.

Zack Philipps
Web Developer at Tribeswell, LLC http://www.tribeswell.com/
zack@tribeswell.com
812.797.9545

[zackphilipps]

I still think sudo should be there by default. The goal is to save time.

[webpro]

@zackphilipps No, using sudo should not be the default:

Installing node as a root user means that installing npm, and npm packages also requires the use of sudo. So, you’ll be installing 3rd party libraries of code that have root access to your entire filesystem. But, you’re reading all of the source code for the libraries you use, right? Right.

[zackphilipps]

That makes sense. I installed with Homebrew and I can't get @Rowno's instructions to work. I updated my pull request though.

[hkdobrev]

@zackphilipps I agree with @Rowno and @webpro. I install everything I can without sudo and prefer the program to ask me when elevated privileges are needed for a specific thing.

[zackphilipps]

I've been convinced, lol. The pull request is changed. 

[hkdobrev]

@zackphilipps Sorry, didn't see that! I welcome the unified install/update mechanism for npm. Do you think you'd be able to change the PR to contain only this change? It seems it contain other changes from your fork perhaps.

[zackphilipps]

Should I make a separate PR for the Dropbox thing? Because I think it's needed. 

[zackphilipps]

Also, this might be a stupid question, but is using sudo for aptitude any different than using sudo for npm? I'm just confused as to why it seems like npm is the only package manager people are worried about.

[hkdobrev]

@zackphilipps I am also updating gems and brew formulae without sudo and I am currently not using aptitude, but I have seen methods to use it with less sudo.

[zackphilipps]

I see. Well I guess this conversation has already been had, and people made the decision to remove sudo from npm and leave it for gems in this dotfile, so I must be spinnin' wheels. But, I learned a little. Thanks for the info guys! I think for now I am just going to take the risk and add sudo to the npm parts on my local copy so I can use the update alias.

Btw I fixed the merge conflicts.