Angular Fullstack 1.2.0 available now

Our much-anticipated 1.2.0 release of the Angular Fullstack generator is available now.

As many MEAN applications require accounts, we’ve added the ability to scaffold a user account boilerplate for your app.

The Passport boilerplate generates:

  • Configuration for Passport and a User model
  • API routes for sign up/log in/log out
  • Login and signup views, with form validation (including handling server validation errors)
  • Angular Auth service for interfacing with the authentication API from the client
  • Settings view that allows you to change your password

This boilerplate is also available in Jade and CoffeeScript flavors.

Try out the demo of what it scaffolds. (Typically needs a refresh to load, as it’s running on a heroku free instance.)

Configuration files are now generated with a new project, making it much easier to change behavior in different node environments. Routes have been separated out of the server.js into their own module.

Additionally, we’ve overhauled the deployment to build all distribution files all into the dist folder. No more public/views folders cluttering up your project folder. And no need for a separate heroku folder anymore, we just use dist.

For more info head over to the github page and have a look at the changelog.

Huge thanks to kjellski for his help bringing Passport integration to the generator!

Update: At time of writing this the npm version was 1.1.1. I’ve corrected this and published 1.2.0 on npm. Please update with npm update -g generator-angular-fullstack if you got the wrong version.

Share Button
  • pebre79

    FYI: MEAN stands for MongoDB, ExpressJS, AngularJS, and NodeJS

    • tylerhenkel

      Yep, thats exactly what I meant. This is a MEAN generator after all

  • Kjellski

    Hey Tyler,

    Just wanted to say thanks for the mention and letting me contribute!

    Greetings from Hamburg, Germany :)

  • Steve Lorimer

    Huge props for this! Great work!

  • Mike Robinson

    Great work on this generator so far. I’ve plugged around with it to get my feet wet — I’m new to using Node on the back end. How do you recommend I go about adding Twitter sign-up with this?

    • tylerhenkel

      The generator only ships with the Local Passport Strategy, however it shouldn’t be too difficult to add other Passport strategies for Twitter or any other OAuth provider. I’d recommend adapting this tutorial to the generated project

      • Mike Robinson

        Thanks so much, I’ll give it a go!

      • Tarrence

        Hi Tyler,

        I’m trying to implement Box OAuth with Passport and running into an issue. I’ve setup the routes and BoxStrategy and when I hit the endpoint it calls passport.authenticate(‘box’) but then it hangs indefinitely. When I step through it seems like it might not be finding the strategy?

        Do you know what could be causing this? The browser spins and the callback never gets called.


        • tylerhenkel

          Hi Tarrence, I might suggest keeping the passport authentication in the routes.js. I was a bit confused about how you were setting up routes in the session controller.

          I just setup my twitter oauth routes like this in routes.js:

          app.get(‘/api/twitter’, passport.authenticate(‘twitter’, {
          failureRedirect: ‘/login’

          app.get(‘/api/twitter/callback’, passport.authenticate(‘twitter’, {
          successRedirect: ‘/’,
          failureRedirect: ‘/login’

          • Tarrence


  • Hereandnow

    great work, as i mentionend in the comments in addy osmani’s blog post about MEAN generators, i like your’s by far most!

    • tylerhenkel


  • Niall O’Brien

    Are server-side views really the best solution with regards to auth etc.? I fail to see how this can be beneficial when writing clients for a multitude of devices (eg. CLI clients). Shouldn’t the API be truly stateless? Correct me if I’m wrong.

  • sph130

    By the way – this is awesome. Wasn’t a mean stack developer – old lamp guy.. and one two weeks later i’ve got a pretty full featured app.

    If i want to collect additional user registration fields and still allow for facebook and google auth in addition to local how would i do that? (like a Company ID – trying to do an automated flow where a company owner invites users they get a unique link (or can paste in the company id during reg)

    Is it possible – can you have the facebook provider once succesful return to an interim page and ask for additional items to update the user with? Any other ideas that would make it as seamless for the user?