Node/NPM/Validator Setup - Mac Table of Contents. Then, run both node -v and npm -v to see the version numbers and check that both commands are installed and working. Jul 21, 2017 Once it's done, you can test to see both node and npm functioning by opening PowerShell (or any shell) and typing node -v and npm -v, which will check the version number. Installation on a Mac or Linux. In order to install everything on a Mac, we'll be running commands in Terminal.app, and Linux distributions vary. Install Node.js and npm.
This tutorial will help you to install Angular.js on your macOS operating system via command line. You must need to install Homebrew package manager on your macOS.
Let’s start the installation of Node.js on your macOS system using Homebrew. So first update the Homebrew package manager index. Then you can install Node.js package in your MacOS system using the following command:
You have successfully installed Node.js on your system. Execute below command on the terminal to view the installed Node.js version info.
After installing the Node.js and npm on your system, use the following commands to install the Angular CLI tool on your system globally.
This command will install the latest available Angular CLI version on your macOS system. If you need any other Angular version on your macOS use one of the following commands as per required version.
Using the -g above command will install the Angular CLI tool globally. So it will be accessible to all users and applications on the system. Angular CLI provides a command
ng used for command-line operations. Let’s check the installed version of ng on your system.
Now, create a new application named hello-angular4 using the Angular CLI tools. Execute the commands to do this:
This will create a directory named hello-angular4 in your current directory, and create an application.
Your basic Angular application is ready to serve. Change directory to hello-angular4 and run your Angular application using ng serve command.
You can access your angular application on localhost port 4200, Which is the default host and port used by Angular application.
You can change host and port for running Angular application by providing –host and –port command line arguments.
The IP address 0.0.0.0 listens on all interfaces and publically accessible.
I find myself writing about this over and over again in the prerequisites of an article I've begun to write. I'd prefer to write one definitive guide to refer to in the future, so here it is.
npm doesn't stand for Node Package Manager*, which means it’s the tool to connect to the repository containing all the Node.js programs, plugins, modules and so on.
*npm actually does not stand for 'Node Package Manager' but essentially that's what it is and does, so most people refer to it that way.
This is the most confusing concept to understand at first, so it's important to let this settle in. Traditionally, you're used to globally installing any sort of program or software on your computer. If you want Spotify, you'll download Spotify, and then it will be available to you.
With npm, you will have some global installs, but mostly everything will be done on a local project basis, meaning you'll have to install everything you need for each project in its own directory. If you want to have a project running Gulp and Sass, you'll create a directory, with a new npm install.
For future reference, any global installations will have the
Installing everything on Windows is a breeze.
Node.js and npm can be installed from a download link. Go to the Node installation page, and download the Node installer. I have a 64-bit Windows 10 OS, so I chose that one.
Once it's done, you can test to see both node and npm functioning by opening PowerShell (or any shell) and typing
node -v and
npm -v, which will check the version number.
In order to install everything on a Mac, we'll be running commands in Terminal.app, and Linux distributions vary.
We’re going to use Node Version Manager (nvm) to install Node.js and npm.
~/.bash_profile file, and make sure
source ~/.bashrc is written in there somewhere. Restart the terminal.
Run the install command.
Run the use command.
Now that Node.js and npm are installed, test them by typing
node -v and
At this point, you're set to start setting up Gulp, Webpack, Browserify, or whatever your aim is. We can also create a simple project to test that everything is working properly.
Navigate to the directory in which you want your project to exist - in my case, sites/node-test.
Now initalize a new project with npm.
The following will pop up in the terminal, and prompt you for a few
First, it will ask for a package name.
The rest you can just press enter and skip. Now you'll notice we have a package.json file that contains all the information we entered.
A package.json is a file that contains metadata about the project, and handles the dependencies (additional software and modules) of the project.
Now, we're going to install our first dependency - a very important and useful package called left-pad, which will add white space to the left side of a string, adding up to a number.
For example, writing this: Libusb 64 download.
Will output this:
left-pad is a package on npm, which as we stated previously contains the registry for all publicly available packages.
To install a dependency with npm, we use the command
npm install dependency-name-here. Now, simply running
npm install will download the dependency, but it won't save it to the project. Since we've already created our package.json, we'll use the flag
--save to install the dependency and add it to package.json.
As long as you ran this command inside the project directory, it will successfully install the dependency by creating a node_modules directory. It will also create a package-lock.json file, which we can ignore. Finally, it updated our package.json file with a new line.
Now the project recognizes the left-pad dependency as existing
You can also run
npm install --save-dev to specify that the dependency will only be used for development (not production) purposes.
Let's create index.js in the root of our directory. This is everything you should have now:
For future reference, don't bother looking in the node_modules rabbit hole. It will get really overwhelming with bigger projects.
In order to use a dependency, we use
require() and put it in a variable, like so:
This will be the entirety of our index.js file, in which we require left-pad, run a
leftPad() function, and send it to the console.
Since Node.js is not recognized by the browser, we'll be testing this in the console. In your shell, run the
node command followed by the filename in the root of your project.
If everything went well, you should have printed
Hello, World! to the console, with two spaces on the left.
In this tutorial, we learned the following:
If you got lost at any point, view the source on GitHub.
With this knowledge, you're ready to start using Gulp, Grunt, Webpack, Browserify, or anything else that depends on Node.js or npm.