Yeoman generator for AngularJS
Yeoman generator for AngularJS - lets you quickly set up a project with sensible defaults and best practices.
npm install -g generator-angular
Make a new directory, and
cd into it:
mkdir my-new-project && cd $_
yo angular, optionally passing an app name:
yo angular [app-name]
grunt for building and
grunt serve for preview
Sets up a new AngularJS app, generating all the boilerplate you need to get started. The app generator also optionally installs Bootstrap and additional AngularJS modules, such as angular-resource (installed by default).
Generates a controller and view, and configures a route in
app/scripts/app.js connecting them.
yo angular:route myroute
This is the myroute view
Explicitly provide route URI
yo angular:route myRoute --uri=my/route
Produces controller and view as above and adds a route to
Generates a controller in
yo angular:controller user
Generates a directive in
yo angular:directive myDirective
angularmodule'myMod'directive'myDirective'returntemplate: '<div></div>'restrict: 'E'link:elementtext'this is the myDirective directive';;;
Generates a filter in
yo angular:filter myFilter
angularmodule'myMod'filter'myFilter'returnreturn 'myFilter filter:' + input;;;
Generates an HTML view file in
yo angular:view user
This is the user view
Generates an AngularJS service.
yo angular:service myService
You can also do
yo angular:value, and
yo angular:constant for other types of services.
Generates an AngularJS service decorator.
yo angular:decorator serviceName
angularmodule'myMod'config$providedecorator'serviceName'// ...return $delegate;;;
In general, these options can be applied to any generator, though they only affect generators that produce scripts.
For generators that output scripts, the
yo angular:controller user --coffee
tl;dr: You don't need to write annotated code as the build step will handle it for you.
By default, generators produce unannotated code. Without annotations, AngularJS's DI system will break when minified. Typically, these annotations that make minification safe are added automatically at build-time, after application files are concatenated, but before they are minified. The annotations are important because minified code will rename variables, making it impossible for AngularJS to infer module names based solely on function parameters.
The recommended build process uses
ng-annotate, a tool that automatically adds these annotations. However, if you'd rather not use it, you have to add these annotations manually yourself. Why would you do that though? If you find a bug
in the annotated code, please file an issue at ng-annotate.
By default, new scripts are added to the index.html file. However, this may not always be suitable. Some use cases:
To skip adding them to the index, pass in the skip-add argument:
yo angular:service serviceName --skip-add
The following packages are always installed by the app generator:
The following additional modules are available as components on bower, and installable via
All of these can be updated with
bower update as new versions of AngularJS are released.
es5-shim have been removed as Angular 1.3 has dropped IE8 support and that is the last version that needed these shims. If you still require these, you can include them with:
bower install --save json3 es5-shim.
wiredep should add them to your index.html file but if not you can manually add them.
Yeoman generated projects can be further tweaked according to your needs by modifying project files appropriately.
You can change the
app directory by adding a
appPath property to
bower.json. For instance, if you wanted to easily integrate with Express.js, you could add the following:
This will cause Yeoman-generated client-side files to be placed in
Note that you can also achieve the same results by adding an
--appPath option when starting generator:
yo angular [app-name] --appPath=public
grunt test will run the unit tests with karma.
See the contributing docs
When submitting an issue, please follow the guidelines. Especially important is to make sure Yeoman is up-to-date, and providing the command or commands that cause the issue.
When submitting a PR, make sure that the commit messages match the AngularJS conventions.
When submitting a bugfix, write a test that exposes the bug and fails before applying your fix. Submit the test alongside the fix.
When submitting a new feature, add tests that cover the feature.
Recent changes can be viewed on Github on the Releases Page