yeoman / generator

Rails-inspired generator system that provides scaffolding for your apps

Generator

Rails-inspired generator system that provides scaffolding for your apps

Getting Started

If you're interested in writing your own Yeoman generator we recommend reading the official getting started guide. The guide covers all the basics you need to get started.

A generator can be as complex as you want it to be. It can simply copy a bunch of boilerplate files, or it can be more advanced asking the user's preferences to scaffold a tailor made project. This decision is up to you.

The fastest way to get started is to use generator-generator, a Yeoman generator to generate a Yeoman generator.

After reading the getting started guide, you might want to read the code source or visit our API documentation for a list of all methods available.

API documentation for v4.x.

Debugging

See the debugging guide.

Contributing

We love contributors! See our contribution guideline to get started.

Sponsors

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

License

BSD license Copyright (c) Google

generator's Issues

Chromeapp needs 16x16 icon

I tried to upload a barebones example from the generated chrome app to the chrome web store and it won't let me upload it because it is missing a 16x16 icon.

Backbone generator does not integrate Require.js in Model,View,Collection,Router

When I run yeoman init backbone:model cars, the generated code does not have integration with Require.js. The same applies to a View, Collection and a Router.

Installation of generators (question)

Hi,
From what I understood while testing Yeoman the generators need to be located in yeoman/cli/lib/generators. So when creating a npm or bower package for a new generator, is there a way to make it install itself in this directory or the user has to do it manually?

Thanks

Angular: app name should be configurable

I'm not very fond of the generator simply using the cwd as the app name. It should be configurable somehow (possible through a command line argument). Also, it shouldn't force the convention of using App as the namespace.

Fix for yeoman/yeoman/pull/522

Fix for http://github.com/yeoman/yeoman/pull/522. Coffee watch causing built failures.

Bootstrap Compass Font Awesome fonts aren't getting included in generator.

First off, there's fragmentation between the fork the yeoman generators are cloning of Boostrap Compass.

https://github.com/kristianmandrup/compass-twitter-bootstrap

Has been updated recently, but the original fork appears to me further update in other aspects.

https://github.com/vwall/compass-twitter-bootstrap

Secondly, the font awesome fonts from /vendor/ don't seem to get copied across during init.
I've looked into writing the necessary code, but i'm not really too sure where to start.

If someone can sort this out, that would be grand.

yeoman init chromeapp hangs after "Writing app/icon-128.png...OK"

$ yeoman init chromeapp
Running "init:yeoman" (init) task
This task will create one or more files in the current directory, based on the
environment and the answers to a few questions. Note that answering "?" to any
question will show question-specific help and answering "none" to most questions
will leave its value blank.

"yeoman" template notes:



        _   .--------------------------.
      _|o|_ |    Welcome to Yeoman,    |
       |_|  |   ladies and gentlemen!  |
     / \Y/ \ o_________________________|
    ||  :  |//
    o/ --- \
      _\ /_

Out of the box I include HTML5 Boilerplate, jQuery and Modernizr.

.. Invoke chromeapp ..

Please answer the following:
[?] What would you like to call this application? (myChromeApp)
[?] Do you need to make any changes to the above before continuing? (y/N)

Writing .npmignore...OK
Writing test/index.html...OK
Writing test/lib/expect.js...OK
Writing test/lib/chai.js...OK
Writing test/lib/mocha/mocha.js...OK
Writing test/lib/mocha/mocha.css...OK
Writing test/runner/mocha.js...OK
Writing .editorconfig...OK
Writing .jshintrc...OK
Writing app/index.html...OK
Writing app/manifest.json...OK
Writing app/.htaccess...OK
Writing app/main.js...OK
Writing app/styles/main.css...OK
Writing app/robots.txt...OK
Writing Gruntfile.js...OK
Writing .gitattributes...OK
Writing package.json...OK
Writing app/manifest.json...OK
Writing app/index.html...OK
Writing app/main.js...OK
Writing app/icon-128.png...OK

Everything seems to be running fine until it gets to Writing app/icon-128.png...OK then it hangs indefinitely.

Installed on a VPS running Ubuntu 11.04.

Missing angular-resource (as option/ default)

Not critical but it would be nuce to have the possibility to include and reference angular-resource as either an option on the main generator or as an optional extra generator.

Add fixes to Require.js/r.js build config.

These were applied to the main yeoman generator but not other generators. Should only have to fix those relying on RequireJS (bbb maybe?).

yeoman init --help doesnt shows available generators

Was following docs on creating custom generators.

My results on running yeoman init --help didnt showed any available generators.

Looked in the source (generators.js) file.

changed generators.lookupHelp method's namespace variable
from: namespace = shorten.split(path.join('/')).slice(0, -1).join(':'),
to: namespace = shorten.split('/').slice(0, -1).join(':'),

being new to javascript, im not sure if this change is appropreate but it does shows all the available generators now.

However, it doesnt shows yeoman: controller in the list as per docs

Issue Submission Checklist:

Made sure you're on the latest version npm update -g yeoman

Check. (0.9.4)

Looked through the list of known bugs to ensure the issue hasn't been noted or solved already

Check

Used the search feature to ensure that the bug hasn't been reported before

Check

What OS and version you're on, etc

Windows 7 32-bit

Shared the output from echo $PATH $NODE_PATH and brew doctor as this can also help track down the issue.

Im sorry I have no idea what this is.
If $PATH means %PATH%
C:\Ruby193\bin;C:\Program Files\Common Files\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Windows Live\Shared;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\nodejs\;C:\node_modules\phantomjs-1.6.1\;C:\Program Files\Sublime Text 2;C:\Program Files\Git\bin;C:\Python27\

Sorry for my bad english :)

Helper for re-writing routes

From: yeoman/yeoman#136

@btford:

I've written a helper for re-writing index.html and app.js to (respectively) include script tags and add routes when the corresponding generator is run. I'm not sure if this functionality lives elsewhere in Yeoman, or if it would be helpful to move it somewhere else so it is more generic and can be reused.

@addyosmani:

That is actually really useful. We have a looser concept around our wiring API, but not something specific to routes. I think this might be a useful concept to apply to other generators.

If someone could point me in the right direction as to where this should ideally live, I'd be happy to refactor it and submit a PR. :)

incorrect usage examples

Did yeoman init used to be yeoman generate in a previous life? Several usage examples displayed by the cli as well as the generators.md doc instruct the user to use yeoman generate which can undoubtedly lead to confusion.

Default template: include non-minified libraries

After generating a test app I found inside app/scripts/vendor the minified versions of modernizr and jquery.
I would like the default generator to not use minified versions of vendor's libraries.
I think minifying should be done latter at a building phase.

Generators for angular with dashes

When I try to generator a route, controller, etc.. with a name like test-again I get a controller with a name of Test-AgainCtrl however I would except TestAgainCtrl like it does if I do test_again. Dashes is a pretty common file naming convention for javascript and would like to see that better supported.

Generator for CanJS

I know that @ralphholzmann is working on a boilerplate for CanJS. We could probably have a very simple generator (similar to bbb for Backbone Boilerplate) written that works with this, unless they'd like something more complex :)

Flesh out dependencies in package.json

generate backbone model/collection/router in coffeescript?

How can I generate backbone model in coffeescript?
I tried yeoman init backbone:model Todo --coffee but failed. I got the model in javascript.

Automatically creating unit tests when generating models, views, controllers, etc.

From yeoman/yeoman#136:

@btford:

I am creating unit specs with the creation of each controller/filter/directive through the generators. So yeoman init angular:controller something creates both app/scripts/controllers/something.js and test/spec/controllers/something.js. I think it would be great if generators for other frameworks would follow suit to promote easier front-end testing.

@addyosmani:

They certainly could. Whilst we haven't demonstrated use of them that greatly just yet, we actually support additional flags that can be passed into a generator at the command-line to specify a default unit testing framework to use for your tests being speccd out. This can defer yeoman to using one testing framework generator over another, but we'll try to improve the unit testing situation post v0.9.

uninstaller asks for you to sudo to 'nobody'

When trying to follow the temporary update commands or trying to uninstall the npm package manually it requests the password for 'nobody'. The root password does not work in this case.

sudo npm uninstall yeoman -g

> [email protected] uninstall /usr/lib/node_modules/yeoman
> sudo rm -r ~/.yeoman

[sudo] password for nobody: 

publish to npm

At some point, we should.

Mostly to be able to depends on yeoman-generators instead of yeoman when creating custom generators.

Yeoman doesn't copy components directory into app folder when the project is generated using bbb generator

From @jsinghfoss

I generated a project using yeoman install bbb. I wanted to install handlebars. So I ran yeoman install handlebars. Which fails for bbb based projects. So in a separate thread I found it's a bower related issue. So, I ran bower directly bower install handlebars which successfully installed handlebars into components directory but failed to create this directory into app folder. So, now when I run yeoman build it doesn't include components directory as it is sitting outside the project.

OS: OS X Mountain Lion
Installed yeoman from master branch
Version 0.9.2

Generator using Bower for packages

We currently demonstrate how to pull in dependencies from GitHub/locally, but now how to do this using Bower. I'd like someone to write a version of quickstart or the yeoman generator which does this, just as a reference for others :)

angular generator: testacular version dependency not listed anywhere

Hi,

I used the angular generator and tried to run a test. I got an error message saying that the config file was no where to be found. It turned out I needed to update the testacular package.

Is the version of the testacular package not listed somewhere as a dependency? Should it be?

Express generator with RESTful crud

https://github.com/jacobmumm/generators/tree/express

@blai is working on getting yeoman server to launch a project-local app script through the Gruntfile. I will have to incorporate whatever changes are necessary in the Gruntfile in order for this to work seamlessly.

I wanted to share what I've done so far to see if it makes sense and to get some feedback. Here's how I would use it.

I would start by creating a client-side app. The express generator can be run on top of this. Angular is my framework of choice, so I would do this:

yeoman init angular
yeoman init express

I have a pull request in now for angular:crud, and my express generator also has crud.

yeoman init angular:crud post
creates:
app/scripts/controllers/post/postIndex.js
app/scripts/controllers/post/postCreate.js
app/scripts/controllers/post/postUpdate.js
app/scripts/controllers/post/postView.js
app/views/post/postIndex.html
app/views/post/postCreate.html
app/views/post/postUpdate.html
app/views/post/postView.html
adds routes to app.js
/post/index
/post/create
/post/update/:id
/post/view/:id

yeoman init express:crud post
creates:
routes/postRoutes.js
app.get("/posts", function(req,res){});
app.get("/post/:id", function(req,res){});
app.post("/posts", function(req,res){});
app.put("/post/:id", function(req,res){});
app.delete("/post/:id", function(req,res){});

adds routes to appRouter.js
require('routes/postRoutes')(app);

Obviously, a lot needs to be done still, but I just wanted to share this in case anyone else was thinking about doing the same.

//cc @btford

Sanitize input

From another issue:

JavaScript variables cannot contain dashes (-).

To reproduce:

mkdir yeoman-test
cd yeoman-test
yeoman init ember

Look at the file yeoman-test/app/scripts/main.js:

var Yeoman-Test = Ember.Application.create();

Proposed solution: replace - with _ (underscore)

Refactor Generators

A number of developers have pointed out that some of the current generators (e.g bbb etc) overwrite existing files that were created using yeoman init. Whilst giving developers a 'complete' boilerplate experience was by design, there have been several requests that we improve them to do one of the following:

• Option 1 - stick to using yeoman init as the baseline and only have generators write on top of this the files that they need. Note: This has the challenge of us needing to manually wire up index.html and other files (e.g RequireJS config) where applicable
• Option 2 - support a developer using yeoman init as a baseline but also someone just using yeoman init generatorName by asking them before overwriting any files for the latter. This would effectively give you the same boilerplate as you would normally get with the generator, but other libraries/options included when yeoman init'ing would also stay in place.

My vote would be for us to go for option 2. This can be fairly easily be implemented using the warnOn functionality we introduced to generators a few weeks ago but never got around to adding.

Side: It doesn't appear that so far anyone has suggested this, but my own personal workflow would have been just using a generator like yeoman init bbb and then yeoman install bootstrap etc, if you needed to add in styling. That said, I'm happy to fly with any of the two above or a different option if there are suggestions.

Unit tests for individual generators

Is there any infrastructure for testing individual generators? I see there are tests for the generator's API, but not for if I wanted to write a unit test for say the Backbone generators in particular.

Classify app's name instead of camelize

Generating an Ember app with yeoman init ember instantiates a myApp variable as the application namespace. Ember conventions warn about this as the variable's name should be capitalized (MyApp) and not just camelized (myApp).

So I have to ask what library is being used that has _.camelize so I can try a PR to solve this. Is it epeli's underscore.string?

Chromeapp png corrupted on project init

When doing an init of a new project using yeoman init chromeapp it creates an app/icon-128.png file. When you attempt to open the file it is corrupted and won't open correctly.

When replaced with the png from the repository it works as expected.

Generator overwriting it's own file

Temp fix in #66

Because of the recently landed conflict handling, it now brings up the conflict prompt even on clean project folder because of the init generator trying to write index.html and main.js multiple times.

We need to figure out a good way to prevent the conflict prompt to appear when init'ing generators that overwrite it's own files.

Mickael suggested we could have a method this.conflicter.off(); to temporary turn it off for the generator in question.

I like that, but I would still like to see an even more transparent way of handling modification to a file cross methods. Something like what I've done in the PR, only more elegant with an API method.

Inferring a framework to avoid having to type someframework: in front of every generator call

From: yeoman/yeoman#136

@btford

My fingers get tired typing yeoman init angular: in front of every generator command. Frameworks can typically be thought of as mutually exclusive, so it seems like once I yeoman init angular I should be able to yeoman init controller and have yeoman infer that I want an AngularJS controller, perhaps based on the contents of app/vendors.

@addyosmani

We currently already support something similar I believe (re: being able to set a default MVC framework) - @mklabs, is this still in place? I remember seeing it in the earlier versions of the generator API.

I'll dig around some as well.

yeoman init output

From yeoman/yeoman#567

as you know, yeoman init executes a generator-- even if no generator is specified the result of yeoman init is really yeoman init yeoman:app.

the initial text output by yeoman init comes from the yeoman init grunt task not the generator that's ultimately used, which would be fine if it was a single line informing the user that yeoman is about to do whatever it was asked to do but it's not, it's 21 lines of text that (more than likely) doesn't apply to the generator you're about to run.

it tells me it's going to ask some questions and instructions how to answer them when my task may or may not ask any questions at all; then after a bunch of blank lines and ascii art, it informs me HTML5 Boilerplate, jQuery and Modernizr are included (again possibly having nothing to do with the ultimate task)

all this pre-generator output seems to jive with what yeoman init does with no arguments so i propose moving all that to the yeoman:app generator and replacing it with something short(er) and generator agnostic.

lastly, to illustrate my point open the terminal and run yeoman init with an invalid or misspelled generator name i.e. yeoman init icantspell ... the error message the user cares about is in there somewhere.

bbb generator livereload issue

Hi,
when using the bbb scaffold generator livereload isn't injected for test/index.html when running server:test task.

This is because lib/generators/bbb/all/templates/test/index.html doesn't have start tag for <html>

Generator fix for yeoman/issues/460

We need to change the path to app/components as a part of yeoman/yeoman#460 for all relevant generators.

Replace lib scripts during build to point to CDN

From: yeoman/yeoman#136

@btford:

I'd like to have <script src="scripts/vendor/angular.js"></script> replaced with the CDN link during the build process. It looks like cli/tasks/usemin could be hacked to add a directive that does this. Maybe just using the existing syntax, and writing something like: <!-- build:js //ajax.google.com/whatever --> in your index.html?

@addyosmani

usemin could indeed be hacked in this way, but we would probably prefer to have local assets over CDN ones until we upgrade all generators to work with Bower packages. A Bower package can still point back to a GitHub repo (or perhaps a CDN), but the benefit of this is that the user would be able to manage their Angular updates via Bower rather than having a static reference.

I have not yet used Bower (it seems that I still don't have access), but my understanding was that it just fetched and maintained front-end packages. This is a little different from what I want to be able to do; I want to be able to define (somewhere) that my app uses AngularJS version x.y.z, and have Yeoman include a local, unminified version when developing, but replace that with a link to the CDN, or do something like:

<script src="//ajax.google.com/whatever.min.js"></script>
<script>window.jQuery || document.write('<script src="js/vendor/whatever.min.js"><\/script>')</script>

...when building the production version. In general, it's easier to debug when you're using unminified libraries, but a specific use case for this feature is that AngularJS replaces more helpful error messages with error codes in the minified version. Another use case is that you might want to be able to develop offline, but reap the benefits of a CDN when in production.

Generator for AngularJS / CoffeeScript / RequireJs / Mocha

While the default generator is not too bad.. it's missing some things that would improve it IMHO.

• CoffeeScript as a language instead of JavaScript
• Mocha as the test library instead of Angulars default of Jasmine. Yes, I know that the Angular guys have a preference at the moment for Jasmine (and their mock APIs have hooks that only work with Jasmine at the moment -- but hopefully that will change)
• Dependency hierarchy rigged up through Require
  • @CaryLandholt has an example here, though I'm not yet sure if this is the simplest approach for connecting the two. This code is a bit of a departure from a stock Angular app wrt to Modules, etc.
• Package management of things like jQuery done through Bower. As I understand it, Bower wants to use a /components directory to store these assets (is there an override?) -- so the Gruntfile needs to be modified to accommodate this.

I just wanted to put the idea out there... and see if this is something that would land in the official generators repo, or in an external one?

init generator is unclear in its Twitter Bootstrap for Compass prompt

When running the init generator, the user is prompted with "Would you like to include Twitter Bootstrap for Compass?" This prompt does not accurately reflect the choice the user is being asked to make.

The prompt seems like it's asking if the user would like to include Twitter Bootstrap or not. Instead, the user must include Twitter Bootstrap and is being asked how they would like it included in the project, either via Compass @import or as file in their styles directory.

The prompt should be changed to avoid user confusion. Some copy suggestions:

"Would you like to include Twitter Bootstrap for Compass? (Declining will place a bootstrap.css file into your styles directory.)"

"Twitter Bootstrap will be included in your project. Would you like to include it via Compass?"

Tests

Now that generators are separated from the core they should have their own test suite. We might be able to port some stuff over from Yeoman.

Integrate Travis when this is done.

.

Unable to install using git protocol

Not sure if this is something that can already be configured in yeoman - but basically, I can't use the git protocol due to IT issues at the workplace. Is this something that can be added in as a configuration?

Thanks!

One more level of generator options?

Hey,

my use case for Yeoman is to generate (and maintain packages) for an offline Angular app. However the current generator assumes it's going to run on the server and creates a lot of things which are not relevant in the context of an offline app (.htaccess, 404.html, favicon, robots.txt, Google Analytics script include, IE conditionals, etc).

So my proposal would be to add another level of generator options. Essentially what I'd like to do is:

yeoman init angular:all:offline

The way I envision this working is being able to conditionally include files from the template folder and also to be able to use some conditionals in the templates inside files and for example wrapping the Google Analytics code into this conditional and only include if it's not an offline app.

I'm not really sure how the templates are evaluated, but here's some pseudo implementation to show what I mean

<% if !offline %>
    <!-- Google Analytics: change UA-XXXXX-X to be your site's ID. -->
    <script>
        var _gaq=[['_setAccount','UA-XXXXX-X'],['_trackPageview']];
        (function(d,t){var g=d.createElement(t),s=d.getElementsByTagName(t)[0];
        g.src=('https:'==location.protocol?'//ssl':'//www')+'.google-analytics.com/ga.js';
        s.parentNode.insertBefore(g,s)}(document,'script'));
    </script>
<% endif %>

Is there anything like this already or does this sound like a something Yeoman should do?

angular generator : adding e2e testing

I added testacular-e2e.conf.js from angular-seed on my project generated with yeoman,
I modifiy :
proxies = {
'/': 'http://localhost:3501/'
};
ang then modify Gruntfile.js by adding :

// Alias the test-e2e task to run testacular instead
grunt.registerTask('test-e2e', 'run the testacular test driver', function () {
var done = this.async();
require('child_process').exec('testacular start testacular-e2e.conf.js --single-run', function (err, stdout) {
grunt.log.write(stdout);
done(err);
});
});

I add some test in test/e2e
and launch yeoman test-e2e

it works fine if you launch 'yeoman server' in another window

so, is it possible to launch e2e test without a server launched ?
do you think to introduce e2e tests in future angular's yeoman generator ?

Harmony Module support doesn't work out the gate

via @jsoverson

On a base yeoman init, the HM and esprima paths config are incorrect and you won't be able to use the HM plugin with requirejs

require.config({
  hm: "app/hm",

  shim:{
  },
  paths: {
    esprima: 'app/scripts/esprima',
    jquery: 'app/scripts/vendor/jquery.min'
  }
});

require(['app'], function(app) {
    // use app here
    console.log(app);
});

Should be

require.config({
  shim:{
  },
  paths: {
    hm : 'vendor/hm',
    esprima: 'vendor/esprima',
    jquery: 'app/scripts/vendor/jquery.min'
  }
});

(either that or a baseurl configuration that makes those paths accurate)

That jquery also points to an incorrect location and is probably related to the esprima config issue. The hm config seems out of place all around.

This is after pulling this morning and doing sudo npm link from the cli dir, if there's an updated way to keep a local build up-to-date, let me know.

EJS template support

From @d4kris

When I init a project with yeoman init backbone, I get a file application.ejs in app/scripts/tempates. This gives the impression that EJS templates are "supported", but from what I can tell, its not included.

I wanted to try without Layoutmanager and solved it by downloading EJS from http://embeddedjs.com/ and including it by hand in index.html. Then I could do this in my View:

    template : new EJS({url: '/scripts/templates/searchForm-template.ejs'}),
    render: function() {
        this.$el.html(this.template.render());
        return this;
    }

What I find confusing and in need of clarification is why yeoman includes a sample ejs template if its not included, is it part of "the opinionated set of tools" in favour of other templating options?

This is a general question regarding all the included frameworks and libraries, when I scan the list of installed packages in the installation I wonder which are included as "indirect dependencies" and which are "preferred"? (I've just started trying to map out the framework jungle and liked the idea of Yeoman as a possible trendsetter, hopefully some of my confusion fog will clear when I get further in digging through the framework docs)

Compass javascripts_dir should be app/scripts/vendor (currently temp/scripts)

I'm pretty sure the default javascripts_dir for compass should be 'app/scripts/vendor'. It is currently 'temp/scripts'.

My understanding of this option is that it is mostly for frameworks that have required javascript assets to copy over to your project.

I'd go ahead and make the changes and do a pull request but I want to get a second opinion first.

yeoman server & Angular

from @Hoverbear

Hi,
If you create an angular project with yeoman init angular, then add a second view to the project (For example views/alt.html) and follow a link to that page it works fine, cool.

However, if I edit the views/alt.html page while running yeoman server yeoman will reload the page and yield a 404 like so:
http://i.imgur.com/UBSwk.png

A working example can be found here: Here
(In theory you can just clone and nav to dir then run yeoman server)

To reproduce:

• Run yeoman server
• Navigate to the /alt link (in red)
• Edit the /views/alt.html file and save.
• Observe a 404.

Previous conversation about this issue is in yeoman/yeoman#584

Missing .git ignores in pretty much all generators

Based on yeoman init --help , I tested for the existence of .gitignore in all of the generators.
It was found missing in :

1. bbb (and bbb:all , not sure if the same or not at this point).
2. backbone (and backbone:all)
3. chromeapp:all
4. ember
5. angular:all
6. ember-started:all
7. quickstart:all

So, bottom line, outside of the default yeoman generator, it is missing in all other generators.

Question: Why does the quickstart template ignore dist folder?

In the quickstart generators templates the .gitginore file ignores the dist folder.

https://github.com/yeoman/generators/blob/master/lib/generators/quickstart/all/templates/.gitignore

Why should we ignore the dist folder?

Isn't the dist folder the one which is used in production and so on? If we are not tracking it, this means we should run yeoman build on the server as well.

What am I missing?

AngularJS module global variable?

Why are the AngularJS templates using a global variable?

https://github.com/yeoman/generators/blob/master/lib/generators/angular/templates/app.js#L4

Instead of creating the variable the module could be created like so:

angular.module('myApp', []) ...

and controllers like this:

angular.module('myApp').controller('mainCtrl', function($scope) { ... });

If there is no reason for using a global variable, I would be happy to create a pull request.

Update Gruntfile paths as a part of server task overhaul

Related to yeoman/yeoman#282