With such tool, upgrading to newer versions of node in the future will be much easier – we will not have to run an installer in your machine again

It’s very useful to be able to quickly change node versions if for example, we have multiple projects to maintain on the same machine, and each project needs different versions of node.

Using a tool like that has several advantages: Why use a command line node versioning tool? To avoid running into any issues with constant reinstallations of node, I suggest the following: instead of overwriting your current version of node with the latest one, let's use a simple command line tool that easily allows switching node versions. We will be using node for frontend tooling purposes and for running our development server, and for that specific purpose, you will usually run into fewer issues if you use the latest version.īut, if you already have node installed (any version almost), there is a much better way to upgrade your node version than to run an installer - why you might not be able to in a company computer. Please make sure not to use the long-term support version (LTS), but the latest version instead. In order to get the best possible development experience, and if you don’t have node yet installed: I advise you to go the website and install the latest version of node:

Setting Up A Node Development Environment Why a Single Page Application, What are the Benefits? What is a SPA? This post is part of the ongoing Angular for Beginners series, here is the complete series:Īngular For Beginners Guide - Getting Started (Setup Environment)Īngular For Beginners Guide: Why Angular? The Top BenefitsĪngular For Beginners Guide - Components vs Directives If you are looking to install Angular in the specific context of an enterprise network, have a look at this post for some tips on how to do that.

Setup an IDE, we are going to be using Webstorm.

Scaffold our first Hello World Angular application.

Learn and install the Yarn Package Manager.

We are going to setup up a development environment that is easily upgradeable and causes minimum problems over time due to things like semantic versioning. This might be one of the largest obstacles for someone just arriving at the Angular Ecosystem, maybe even more so than the reactive concepts – getting that environment setup right from the start is crucial. Let's make sure that we have the best development experience possible and don’t run into constant development environment problems. This post is a guide for setting up a solid development environment, for having the best Angular learning and working experience.

Download angular phpstorm