##Install yo
npm install -g yo grunt-cli bower
##AngularJS generator
npm install -g generator-angular
##Make a new directory, and cd into it:
mkdir AngularJS_generator && cd $_
##Run yo angular, optionally passing an app name:
yo angular AngularJS_generator
Generates a controller and view, and configures a route in app/scripts/app.js connecting them.
Example:
Produces app/scripts/controllers/myroute.js:
angular.module('myMod').controller('MyrouteCtrl', function ($scope) {
// ...
});Produces app/views/myroute.html:
<p>This is the myroute view</p>
Generates a controller in app/scripts/controllers.
Example:
yo angular:controller user
Produces app/scripts/controllers/user.js:
angular.module('myMod').controller('UserCtrl', function ($scope) {
// ...
});Generates a directive in app/scripts/directives.
Example:
yo angular:directive myDirective
Produces app/scripts/directives/myDirective.js:
angular.module('myMod').directive('myDirective', function () {
return {
template: '<div></div>',
restrict: 'E',
link: function postLink(scope, element, attrs) {
element.text('this is the myDirective directive');
}
};
});Generates a filter in app/scripts/filters.
Example:
yo angular:filter myFilter
Produces app/scripts/filters/myFilter.js:
angular.module('myMod').filter('myFilter', function () {
return function (input) {
return 'myFilter filter:' + input;
};
});Generates an HTML view file in app/views.
Example:
Produces app/views/user.html:
<p>This is the user view</p>
Generates an AngularJS service.
Example:
yo angular:service myService
Produces app/scripts/services/myService.js:
angular.module('myMod').factory('myService', function () {
// ...
});There are options for each of the methods for registering services. For more on using these services, see the module API AngularJS documentation.
Invoked with --factory
This is the default method when creating a service. Running yo angular:service myService --factory is the same as running yo angular:service myService
Invoked with --service
Invoked with --value
Invoked with --constant
In general, these options can be applied to any generator, though they only affect generators that produce scripts.
For generators that output scripts, the --coffee option will output CoffeeScript instead of JavaScript.
For example:
yo angular:controller user --coffee
Produces app/scripts/controller/user.coffee:
angular.module('myMod')
.controller 'UserCtrl', ($scope) ->A project can mix CoffeScript and JavaScript files.
By default, generators produce unannotated code. Without annotations, AngularJS's DI system will break when minified. Typically, these annotations the make minification safe are added automatically at build-time, after application files are concatenated, but before they are minified. By providing the --minsafe option, the code generated will out-of-the-box be ready for minification. The trade-off is between amount of boilerplate, and build process complexity.
yo angular:controller user --minsafe
Produces app/controller/user.js:
angular.module('myMod').controller('UserCtrl', ['$scope', function ($scope) {
// ...
}]);Unannotated:
angular.module('myMod').controller('MyCtrl', function ($scope, $http, myService) {
// ...
});Annotated:
angular.module('myMod').controller('MyCtrl',
['$scope', '$http', 'myService', function ($scope, $http, myService) {
// ...
}]);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 ngmin, a tool that automatically adds these annotations. However, if you'd rather not use ngmin, you have to add these annotations manually yourself.
The following packages are always installed by the app generator:
- angular
- angular-mocks
- angular-scenario
The following additional modules are available as components on bower, and installable via bower install:
- angular-cookies
- angular-loader
- angular-resource
- angular-sanitize
All of these can be updated with bower update as new versions of AngularJS are released.
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:
{
"name": "yo-test",
"version": "0.0.0",
...
"appPath": "public"
}
This will cause Yeoman-generated client-side files to be placed in public.
For tests to work properly, karma needs the angular-mocks bower package.
This script is included in the bower.json in the devDependencies section, which will
be available very soon, probably with the next minor release of bower.
While bower devDependencies are not yet implemented, you can fix it by running:
bower install angular-mocks
By running grunt test you should now be able to run your 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.
Folked: https://github.com/yeoman/generator-angular
BSD license
