Question

The shell forgets that node and npm are installed every time I log in or switch to a different user.

Whenever I log in or switch back to my main user account, the shell throws “command not found” errors for node and npm. In order to make it work, I have to run $ source ~/.profile; npm use 0.10.17. After that, the node command works again.

On IRC, someone suggested adding these commands to my .bashrc file, but when I did that, loading .bashrc hangs indefinitely. As a Mac user, I’m used to using .bash_profile like this, but this isn’t working like I expected. What is the path to enlightenment on this?


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

P.S.: I’ve fixed your post :]

Try running <code>su -l join</code> instead. This spawns a login shell (and not just an interactive bash shell) which sources .profile and .bashrc. <br> <br>Let me know if that works!

</code> Ugh, there’s no edit button, and my code element wasn’t closed.