You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I added grunt-cli as dependency of my own web app, together with other grunt plugins.
(I want grunt-cli to be part (and version freezed) of the app repo).
But when I run it this way it fails because grunt can't be found, adding grunt dependency solves the problem.
I notice grunt is added as a devDependency of this module, shouldn't it be a regular dependency?
Or we just need to remember to always include grunt in our package.json if we include grunt-cli?
The text was updated successfully, but these errors were encountered:
Grunt should be installed locally to every project. The only job of the CLI is to launch whatever local version of grunt is found. In short, yes, add whatever version of grunt you'd like to use to your package.json. If you want to see how other teams are handling this sort of thing, check out the docs for http://yeoman.io.
I added grunt-cli as dependency of my own web app, together with other grunt plugins.
(I want grunt-cli to be part (and version freezed) of the app repo).
But when I run it this way it fails because grunt can't be found, adding grunt dependency solves the problem.
I notice grunt is added as a devDependency of this module, shouldn't it be a regular dependency?
Or we just need to remember to always include grunt in our package.json if we include grunt-cli?
The text was updated successfully, but these errors were encountered: