Angular Fullstack 2.0: Released

Version 2.0 of the Angular Full-Stack Generator has been released. Here are the highlights:

  • Use Googles AngularJS project structure recommendations for client side.
  • Use a modular structure for the express server
  • Major improvements to auth, including modularization, support for role based auth, using JWT instead of cookies, and optional social auths for facebook/twitter/google
  • Added endpoint generator: generates model / route / controller / test / socket
  • Cleaner separation between client and server. The server views folder no longer contain angular templates
  • Automatic injection of new scripts/stylesheets into the app with grunt
  • Support for UI Router,, and Less
  • Use ng-templates to concatenate all the html/jade views into the javascript payload
  • Rewrote generator to be more modular and testable
  • New look to starter app with basic crud interface.
  • Built in support for protractor e2e tests

For some more in-depth explanation of the new features, check out the write up.

Have fun and happy coding!

Share Button
  • chovysblog

    will the previous version still be maintained in its own branch?

    • tylerhenkel

      Yes, I will be continuing maintenance for 1.x.

  • Victor Mejia

    thanks for your awesome work!

  • Marcus Nielsen

    At least some serious file structure! I had given up hope.

  • Christian Huening

    Awesome! Is there any update path from 1.x to 2.x?

  • robertwalsh0

    Thanks so much for all the hard work! I love this generator. I hope the community rallies behind it!

  • Shote


  • karthi balaj


  • Ted Jenkins

    This is great Tyler, thanks! I can now deprecate my token-based version, based off of 1.x…

  • moussaoui91

    really great job !

  • James Meyer

    It literally took me months to write all that boilerplate code that angular-fullstack does in minutes. Its absolutely amazing but pisses me off so much.

  • Kimball Johnson

    Like the other’s I admire this implementation. Thanks very much for applying your skill to this project! Having spent a month with it, I’m now trying to deploy in a professional manner to Heroku. But I’m not understanding your strategy regarding running heroku commands and the yo commands from the dist folder. The readme’s comments about deploying with yo, maintaining with buildcontrol, and running all commands from the dist folder seem to be in contrast to the heroku strategy.