Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

grunt as dependency #16

Closed
benjamine opened this issue Apr 4, 2013 · 3 comments
Closed

grunt as dependency #16

benjamine opened this issue Apr 4, 2013 · 3 comments

Comments

@benjamine
Copy link

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?

@tkellen
Copy link
Member

tkellen commented Apr 5, 2013

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.

@tkellen tkellen closed this as completed Apr 5, 2013
@benjamine
Copy link
Author

Makes sense, thanks a lot!

@tkellen
Copy link
Member

tkellen commented Apr 5, 2013

Sure thing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants