I keep running into the same problem whenever I set up a fresh Ubuntu 14.04 system. After installing npm through the package manager, trying to install global packages fails with permission errors.
Here’s what I typically do:
sudo apt-get install npm
npm install -g webpack
The global install command throws permission errors related to local lib and bin folders. Running the install command with sudo isn’t a good solution for this particular package.
I found a workaround that involves changing ownership and permissions:
This works for my single-user setup, but I’m wondering if there’s a better approach that would be safer to recommend to others. Is this the standard way to handle this situation, or should I be looking into reporting this as a packaging issue?
Ubuntu 14.04’s npm package is notorious for this exact problem. Your ownership fix works, but it’s risky - you’re messing with system directories that other processes need. I’ve hit this countless times in enterprise setups where touching /usr/local wasn’t allowed. Best fix I found? Ditch Ubuntu’s ancient npm and install Node.js straight from NodeSource’s repo. Their packages are set up right and handle global installs without permission headaches. Just add their repo, nuke the existing npm, then install nodejs from NodeSource. Their package sets up npm’s global directories properly and kills these permission issues for good. You keep your system secure and get stable npm that won’t break when Ubuntu updates.
Been there countless times. Permission issues are a nightmare and fixing them manually gets old quick.
I automated my entire dev environment setup. Every new Ubuntu instance runs a workflow that handles node/npm installation correctly from day one.
It installs nvm, sets the right node version, configures npm prefix to dodge permission headaches entirely, and grabs all my global packages. Takes 2 minutes and I’m done.
When new team members start, they run the same automation and get identical environments. No more “works on my machine” drama or walking anyone through manual fixes.
Built this with Latenode since it handles shell commands and logic flows perfectly. Way cleaner than bash scripts that break every Ubuntu update.
for sure! nvm makes life way easier. you can handle node version switching like a pro, and those pesky perms issues just go away. hands down a smoother ride than wrestling with sudo!
Had the same problem when deploying apps across multiple Ubuntu servers. Yeah, changing ownership works, but it’s a pain because system updates keep messing with those directories again. What fixed it for good was telling npm to use a completely different global directory. I just create a .npm-global folder in the user’s home directory and set npm’s prefix to point there. Now npm installs global packages somewhere the user already owns, and it doesn’t touch system directories at all. Setup’s pretty simple and survives system updates. I’ve run this on production servers for over two years - zero permission issues or security problems. Plus it makes backing up and restoring dev environments way easier since everything stays in user space.
Honestly, just use yarn instead of npm for globals. It installs way cleaner and doesn’t have these weird permission quirks that npm loves throwing at you. I’ve been using it for years on Ubuntu and never had to mess with ownership stuff.
The permission dance gets old fast when you’re spinning up multiple environments. I’ve hit this same headache across dozens of Ubuntu instances.
Automating the entire Node setup saved my sanity. Instead of fighting system directories or manually tweaking permissions every time, I built a workflow that handles everything cleanly.
It downloads the official Node binary, extracts it to a user directory, updates PATH, and installs all needed global packages. No sudo anywhere. No touching system folders that updates can break.
The workflow runs on fresh Ubuntu boxes and gives me identical environments every time. New team members get the same setup in minutes without manual config.
I use Latenode for this - it handles file downloads, shell commands, and environment variables seamlessly. Way more reliable than juggling package managers or hoping system packages work.