Getting an error on your npm install can be a bummer. To avoid a bad showdown, make sure you’ve properly configured your npm install. If you’re using Ubuntu, it’s best to install Node through a default repository. Likewise, be sure you have enabled auto-completion of your package names. Finally, it’s a good idea to check your packages periodically, so you’re always up to date on what’s new. You can even use a cron job to automate the process.
While you’re at it, you may want to try installing some of the more obscure Node JS packages, too. Those aforementioned neophytes may have to wait a while, but you can bet your bottom dollar they’ll be worth it. After all, if you’re planning to develop a large web application, you’ll eventually need to get up to speed on the latest Node JS features and idiosyncrasies. This is especially true if you’re developing an app with a modular architecture.
If you’re in a pinch, you can also install npm on your desktop, which is a lot more convenient. Alternatively, you can use an npm install on your barebones server to ensure you’re always up to date on the latest and greatest Node JS offerings. A side benefit of using the cloud is that you can get a fresh install of npm without having to deal with the hassles of manually transferring files and folders to your new machine. Lastly, the cloud may be a great way to test new Node JS tidbits before you’ve even had a chance to read them all. You’ll also have access to all your favorites in a centralized location, which will only help you decide which neophytes to leave behind.
For the best results, try not to install Node JS on the same machine as your other apps. This will ensure you get the best Node JS experience possible. Likewise, avoid installing it on a shared network, as you’ll run into trouble later on. Finally, it’s best to keep in mind that Node JS comes with its own set of requirements, which will only serve to improve your overall developer experience.