Yeoman generator for AngularJS with Express server
A generator for AngularJS, integrated with an Express
full stack development.
This generator is simply a modification of angular-fullstack to use Stylus/Nib.
I wanted a yeoman generator that used Jade, Stylus, Coffeescript, and Express, so I created this. I was about to name it "angular-jsce" but that didn't look good and "jsce" sounds like "juice" hence "angular-juice".
npm install -g generator-angular-juice
Make a new directory, and
cd into it:
mkdir my-new-project && cd $_
yo angular-juice, optionally passing an app name:
yo angular-juice [app-name]
Launch your express server in development mode.
Launch your express server in production mode, uses the minified/optimized production app folder.
grunt serve will watch client files in
app/, and server files inside
lib/, restarting the Express server when a change is detected.
While deployment should be easy enough with the
grunt dist build, we provide an extremely simplifed deployment process for heroku.
yo angular-juice:deploy heroku for generating a deployment ready folder for heroku.com from your project files.
Create and Deploy an app in 4 steps
mkdir foo && cd foo
yo angular-juice:deploy heroku
cd heroku && git push heroku master
Optional (if using mongoDB)
heroku addons:add mongohq
That's it! Your app should be live and shareable. Type
heroku open to view it.
Note: Generators are to be run from the root directory of your app.
Sets up a new AngularJS app, generating all the boilerplate you need to get started. The app generator also optionally installs Twitter Bootstrap and additional AngularJS modules, such as angular-resource (installed by default).
Initalizes a heroku app and generates a
heroku folder which is ready to push to heroku.
yo angular-juice:deploy heroku
After app modifications run:
then commit and push the heroku folder.
Generates a controller and view, and configures a route in
app/scripts/app.js connecting them.
yo angular-juice:route myroute
This is the myroute view
Generates a controller in
yo angular-juice:controller user
Generates a directive in
yo angular-juice:directive myDirective
angularmodule'myMod'directive'myDirective'returntemplate: '<div></div>'restrict: 'E'link:elementtext'this is the myDirective directive';;;
Generates a filter in
yo angular-juice:filter myFilter
angularmodule'myMod'filter'myFilter'returnreturn 'myFilter filter:' + input;;;
Generates an HTML view file in
yo angular-juice:view user
This is the user view
Generates an AngularJS service.
yo angular-juice:service myService
You can also do
yo angular-fullstack:value, and
yo angular-fullstack:constant for other types of services.
Generates an AngularJS service decorator.
yo angular-juice: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 views, the
--jade option will output Jade instead of HTML.
yo angular-juice --jade
Changes the rendering engine from EJS to Jade, and generates your views as jade files instead of HTML.
Assets that will be minified or compressed such as scripts, styles, and images, must still use normal html tags so they can be picked up by grunt-usemin and compressed for production builds.
For generators that output scripts, the
yo angular-juice:controller user --coffee
the generator finds any in the project), use
Related Issue #452: This option is being removed in future versions of the generator. Initially it was needed as ngMin was not entirely stable. As it has matured, the need to keep separate versions of the script templates has led to extra complexity and maintenance of the generator. By removing these extra burdens, new features and bug fixes should be easier to implement. If you are dependent on this option, please take a look at ngMin and seriously consider implementing it in your own code. It will help reduce the amount of typing you have to do (and look through) as well as make your code cleaner to look at.
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. 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-juice:controller user --minsafe
angularmodule'myMod'controller'UserCtrl' '$scope'// ...;
angularmodule'myMod'controller'MyCtrl''$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.
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-juice: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.
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
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.