Node package ( Grunt ) installed but not available

by

The command line tools are not included with the latest version of Grunt (0.4 at time of writing) instead you need to install them separately.

This is a good idea because it means you can have different versions of Grunt running on different projects but still use the nice concise grunt command to run them.

So first install the grunt cli tools globally:

npm install -g grunt-cli

(or possibly sudo npm install -g grunt-cli ).

You can establish that’s working by typing grunt --version

Now you can install the current version of Grunt local to your project. So from your project’s location…

npm install grunt --save-dev

The save-dev switch isn’t strictly necessary but is a good idea because it will mark grunt in its package.json devDependencies section as a development only module.

More Related Contents:

  1. Find the version of an installed npm package
  2. NodeJS require a global module/package
  3. How to install a private NPM module without my own registry?
  4. How can I specify the required Node.js version in package.json?
  5. What is the difference between –save and –save-dev?
  6. error: This is probably not a problem with npm. There is likely additional logging output above
  7. How to clean node_modules folder of packages that are not in package.json?
  8. How to fix npm throwing error without sudo
  9. Is there a way to make npm install (the command) to work behind proxy?
  10. npm install private github repositories by dependency in package.json
  11. Cannot install packages using node package manager in Ubuntu
  12. npm ERR cb() never called
  13. Node – was compiled against a different Node.js version using NODE_MODULE_VERSION 51
  14. How to edit a node module installed via npm?
  15. Why does “npm install” rewrite package-lock.json?
  16. How to install a node.js module without using npm?
  17. Change default global installation directory for node.js modules in Windows?
  18. Is there any way to configure multiple registries in a single npmrc file
  19. How can I publish an npm package with distribution files?
  20. How to fix npm vulnerabilities manually?
  21. npm install -g less does not work: EACCES: permission denied
  22. How to resolve Node.js: “Error: ENOENT: no such file or directory”
  23. Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (88)
  24. Can’t install any packages in Node.js using “npm install”
  25. npm: Why is a version “0.1” invalid?
  26. How to organise file structure of backend and frontend in MERN
  27. npm doesn’t work, get always this error -> Error: Cannot find module ‘are-we-there-yet’
  28. Can’t install any package with node npm
  29. What’s the difference between dependencies, devDependencies, and peerDependencies in NPM package.json file?
  30. Getting 404 when attempting to publish new package to NPM

Leave a Comment