yeoman / generator-gruntfile

Create a basic Gruntfile with yo.

Welcome, Friend!

Yeoman is a robust and opinionated set of tools, libraries, and a workflow that can help developers quickly build beautiful, compelling web apps.

Website   Getting Started   Submit Issue

Code of Conduct

Everyone in this community (from core members to random committers and volunteers) are asked to please act in accordance with the Yeoman Community Contributor Code of Conduct. We encourage you to follow these social rules which help guide our interactions with each other, and ensure we provide a safe environment for everyone. We aim to make Yeoman a positive, welcoming, open and inclusive project and community.

Code of Conduct

Issue Submission

Make sure you've read the issue submission guidelines before you open a new issue.

Yeoman is composed of a number of different sub-projects, most of which have their own dedicated repository. If you are looking for a repo for a particular piece, you'll find it on the organization page.

Feature requests

Feature requests should be submitted to the repo it concerns. Submit to yeoman/yeoman if you're unsure, otherwise the repositories for our officially maintained generators can be found here.

Contribute

See the contributing docs

Support

Need help or have a question?

• Stack Overflow
• Gitter chat

Please don't use the issue trackers for support/questions.

Links

• Website
• Development discussions
• Twitter
• Media kit
• Discover Bower packages

Team

Yeoman is beautifully crafted by these people and a bunch of awesome contributors

Addy Osmani	Sindre Sorhus	Pascal Hartig	Stephen Sawchuk	Simon Boudrias

Brian Ford	Eddie Monge	Paul Irish	Hemanth.HM	Revath S Kumar

Jimmy Moon	Frederick Ros	Mickael Daniel	Eric Bidelman	Matija Marohnić

Kevin Mårtensson	Arthur Verschaeve	Michael Kühnel	Mehdy Dara	Ulises Gascon

Backers

Love Yeoman work and community? Help us keep it alive by donating funds to cover project expenses!
[Become a backer]

License

BSD license Copyright (c) Google

generator-gruntfile's Issues

Breaks on init

It just breaks when I try to run the generator. My node version is 0.10.15

$ yo gruntfile

TypeError: Cannot redefine property: underline
    at Function.defineProperty (native)
    at addProperty (/usr/local/lib/node_modules/generator-gruntfile/node_modules/grunt/node_modules/colors/colors.js:53:12)
    at /usr/local/lib/node_modules/generator-gruntfile/node_modules/grunt/node_modules/colors/colors.js:189:3
    at Array.forEach (native)
    at Object.<anonymous> (/usr/local/lib/node_modules/generator-gruntfile/node_modules/grunt/node_modules/colors/colors.js:184:3)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

Sub generator, gruntfile:install

I'm thinking that, for example yo gruntfile:install grunt-contrib-clean, it would effectively

• npm install --save-dev grunt-contrib-clean
• insert grunt.loadNpmTasks('grunt-contrib-clean') into Gruntfile.js

And or yo gruntfile:install (no arguments)

• Choice of listing grunt-contrib-* packages or search for a grunt-* package

As far is implementing, I wasn't sure the cleanest way to go about the npm install, whether doing a require('npm') or exec('npm install ...') would be better. I also know (think i know) that somewhere in the yeoman-generator there's some functionality to install npm dependencies, but finding the correct version and updating package.json is already done so well by npm(1).

Thoughts?

You don't seem to have a generator with the name gruntfile installed.

You don't seem to have a generator with the name gruntfile installed.

Create package.json if requested

Just wondering if adding an option to create a package.json would be useful?

Generator Test Framework Composition

How does generator composition work when each scaffolds a different framework?

If each generator registered its supported frameworks Yo could prompt the user for their preferred framework showing the number of generators that support a given framework.

Which test framework would you prefer?
    mocha   6/10
    jasmine 4/10
    qunit   2/10
    nodeunit

Continue prompting for all remaining generators.

Any others?
    jasmine 4/4
    qunit   2/4
    defaults

If the user selects defaults warn which generators did not support their preferred framework(s). Perhaps they'll send a pull request? The frameworks would be stored in .yo-rc.json.

The following generators will use their default test framework:
foo, bar, baz, quox

What if none of the generators registered a framework? Yo could scaffold a generic framework.

Compass watching multiple levels of files/folders by default

I'm not sure if this is the correct place to add this but I think it would be beneficial to have the compass watch look at mulitple levels of files and folders by default.

I have been experimenting with a starter compass project that has multiple folders within the /styles/ css folder.

It has taken me weeks of playing around finding out how to do this in order to come to the conclusion that the default compass watch is limited.

Here's what I'd like to suggest by default:

compass: {
    files: [ '<%= yeoman.app %>/styles/**/*.s{c,a}ss'],
    tasks: ['compass']
}

Sorry if this is the wrong repository but I'll gladly move this ticket to the correct one if you let me know where to put it.

UNMET PEER DEPENDENCY yo@>=1.0.0

UNMET PEER DEPENDENCY yo@>=1.0.0

npm WARN EPEERINVALID [email protected] requires a peer of yo@>=1.0.0 but none was installed.

Spaces replace the hyphen on package names

Hi @addyosmani
I noticed that when you have a project with hyphens the generated gruntfile replaces them with spaces. Consider the following:

{
  "name": "appify-components",
  "version": "0.0.0",
  "dependencies": {},
  "devDependencies": {
    "grunt": "~0.4.2",
    "grunt-contrib-watch": "~0.5.3",
    "grunt-contrib-concat": "~0.3.0",
    "grunt-contrib-uglify": "~0.2.7",
    "grunt-contrib-jshint": "~0.7.2",
    "grunt-contrib-qunit": "*"
  }
}

dist: {
                src: ['lib/appify components.js'],
                dest: 'dist/appify components.js'
            }

I am happy to work on a PR for this issue but wanted to make sure this was not done by design first.

Dependency problems with Yo

Installing this template generates errors, see below:

npm ERR! peerinvalid The package yo does not satisfy its siblings' peerDependenc
ies requirements!
npm ERR! peerinvalid Peer [email protected] wants yo@~1.0.3
npm ERR! System Windows_NT 6.1.7601
npm ERR! node -v v0.10.20
npm ERR! npm -v 1.3.11
npm ERR! code EPEERINVALID
npm ERR!
npm ERR! not ok code 0

Any ideas? Thanks

grunt isn't building out of the box

This needs to be fixed.