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 Collections #379

Closed
tkellen opened this issue Aug 23, 2012 · 0 comments
Closed

Grunt Collections #379

tkellen opened this issue Aug 23, 2012 · 0 comments
Milestone

Comments

@tkellen
Copy link
Member

tkellen commented Aug 23, 2012

per request, here is my comment from cowboy/grunt#377 in a separate issue.

Grunt collections is a concept whereby an npm package can be created with nothing but a list of gruntplugin dependencies. When loadNpmTask is called on this type of package (the heuristic is a package with the keywords gruntplugin and gruntcollection), it will automatically invoke loadNpmTasks for each dependency from within that package.

Here is a mocked directory structure for grunt collections:
https://github.com/tkellen/grunt-collection

The primary driver behind this is allowing grunt-contrib to be broken into separate tasks, but still be installable as a whole. Also, it lets end-users easily create their own set of common-use plugins from various sources.

The package "grunt-collection" is available on npm for testing.

@cowboy cowboy closed this as completed in 4d5d50b Aug 27, 2012
samccone pushed a commit to samccone/grunt that referenced this issue Jul 24, 2014
fix(watch): preserve options parameter if no callback
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