The ability to reply to discussions is limited to PRO members. Want to join in the discussion? Click here to subscribe now.

Angular Automation: Installing Gulp Globally and Locally

Angular Automation: Installing Gulp Globally and Locally

4:24
In this lesson, we learn how to get up and running with Gulp by initializing our project with ```npm init``` and then installing the Gulp CLI globally and then installing it locally to our project. We finish the lesson off by creating our first Gulp file and running our first Gulp task.
Watch this lesson now
Avatar
egghead.io

In this lesson, we learn how to get up and running with Gulp by initializing our project with
npm
init
and
then installing the Gulp CLI globally and then installing it locally to our project. We finish the lesson off by creating our first Gulp file and running our first Gulp task.

Avatar
David

If you're having to use sudo to install with npm, you just have a permission issue, which is very easy to fix.

I've seen a few devs have that issue when they install node with homebrew. If this applies to you, the following has worked for me and other devs before:

sudo chown -R whoami /usr/local

Avatar
Kendrick

I use nvm (Node Version Manager) to install and maintain multiple version of node and npm. The bi-product of this process is that it installs the node version and all it's globals in my home directory under ~/.nvm/versions. No permissions issues, and I have a layer of administrative controls over the versions of node and npm I use, including the ability to easily update and move between versions.

In reply to David
Avatar
Prasanth

Wouldn't recommend this, nvm can be used to avoid this hammer approach.

In reply to David
Avatar
Prasanth

Great introduction, small note. Current best practice is to install gulp-cli globally, instead of gulp itself. All other steps remain the same. More information over at the official docs.

HEY, QUICK QUESTION!
Joel's Head
Why are we asking?