Yeoman Generator for MEAN Seed / MEAN Stack (AngularJS, node.js app) - MongoDB, Express, Angular, Node, Grunt, Bower, Yo. 'Core' and 'Module' subgenerators for customization outside of that.
JavaScript HTML CSS
Latest commit f6a0648 Nov 23, 2015 @nrane9 nrane9 chore: update dependencies
Failed to load latest commit information.
app feat(node-controller): new generator to create CRUD backend API route Feb 8, 2014
common feat: add helper-core-merge to run updates on a SEPARATE branch to th… Dec 1, 2013
core-default-angular chore: update dependencies Nov 23, 2015
core-default-node chore: update dependencies Nov 23, 2015
core-default feat: add httpRedirectPort and some final ssl touches May 2, 2014
core-scss-angular chore: update dependencies Nov 23, 2015
core-scss feat: add httpRedirectPort and some final ssl touches May 2, 2014
docs docs: roadmap update Mar 27, 2014
helper-commands fix: get spawnCommands working on mac. Also update npm dependencies Jul 13, 2015
helper-core-commands-init fix: get spawnCommands working on mac. Also update npm dependencies Jul 13, 2015
helper-core-merge docs: remove comment Dec 2, 2013
helper-log-next-steps chore: add helper- prefix to helper subgenerators Nov 26, 2013
ng-directive chore: update unit test templates Dec 28, 2013
ng-route chore(ng-route): update app.js to new auth structure (remove noLoginR… Dec 28, 2013
ng-service chore: update unit test templates Dec 28, 2013
node-controller refactor: social login - switch facebook to be manual login flow and … May 7, 2014
test init Nov 11, 2013
yo-configs feat: add httpRedirectPort and some final ssl touches May 2, 2014
.editorconfig init Nov 11, 2013
.gitattributes init Nov 11, 2013
.gitignore style: add grayLight1 color Jan 14, 2014
.jshintrc init Nov 11, 2013
.travis.yml init Nov 11, 2013 chore: update dependencies Nov 23, 2015
Gruntfile.js feat(node-controller): new generator to create CRUD backend API route Feb 8, 2014
LICENSE init Nov 11, 2013 docs May 6, 2015
package.json chore: update dependencies Nov 23, 2015


Yeoman Generator for MEAN-seed - MongoDB, Express.js, AngularJS, Node.js + Yeoman (Grunt, Bower, Yo) + Jasmine, Karma, Protractor (for automated testing)

Demo & Tests

Learn to Code with MEAN Stack

Walkthrough course to use this Generator and MEAN stack in general

Getting Started

NOTE: This assumes you already have the necessary programs (i.e. Git, Node.js, MongoDB, PhantomJS) installed; see here for Mac or here for Windows or here for Linux

Install Yeoman Yo, Bower, Grunt and other global node modules we'll need, if you don't have them already:

$ npm install -g yo bower grunt-cli jasmine-node karma yuidocjs forever less

Install this generator:

$ npm install -g generator-mean-seed

Naviagate to a (new) directory where you want to create your AngularJS and node.js app and initiate the generator then follow the prompts:

$ yo mean-seed
  • NOTE: you can also (first) create a yo-configs folder with .json files for the prompts so you don't have to type them all out. This is useful for storing multiple different configurations for different projects - just tell the generator which config to use and you're all set! See the yo_configs folder for examples.

  • NOTE: if you get errors (i.e. npm or bower install failures or timeouts, which aren't uncommon), just re-run the command yo mean-seed OR re-run just the problematic parts, i.e. bower update && bower install and/or npm install. Once everything has installed properly, just make sure to run grunt: grunt q

  • NOTE: if you get an EACCESS / permission denied error during the npm install, find the folder that had permissions issues (from the log output) and run sudo chown -R $USER [path to problematic folder].

See here for more/full info and steps.

Next Steps

  • See the generated file in your new mean-seed app!


You CAN and SHOULD keep your project up to date with the core (seed) generator you used as it goes through version upgrades. Just re-run:

Ensure the generator is up to date:

npm install -g generator-mean-seed

Pull in updates to your project (core/seed - make sure to select the same core you used originally). Just type 'a' (for overwrite all) if you get prompted about file conflicts - we'll handle those with Git merge later so it's safe to overwrite everything in the generator branch.

yo mean-seed

Then if you push, make SURE to ALSO push the/any yo branches (i.e. git push origin yo-core-default) so other developers get that branch and stay up to date.

See for more info.

(Sub)Generators List

  • core-default
  • core-scss
  • ng-route
  • ng-directive
  • ng-service
  • node-controller

See the docs/generators folder for more info.

More generators coming - feel free to create one and submit a pull request!

Documentation / More Info

See the generated file and the docs folder for all documentation. Each (sub)folder typically has an file - start there. Some key docs (roughly in order of priority) listed below:


What is Yeoman?

If you'd like to get to know Yeoman better and meet some of his friends, Grunt and Bower, check out the complete Getting Started Guide.


MIT License

Roadmap / To do



  • while you can fork on Github, we're actually trying a new approach of leveraging Yeoman for different 'core' builds to avoid all the forks. The reason for 'forking' a project is to change it and add functionality that conflicts with or would add too much code bloat to the original repository. However, with Yeoman, we can add EVERYTHING into this ONE project and by using generators, the end user/developer can take ONLY what (s)he wants. So there's no code bloat or worry of this becoming a "kitchen sink" seed with too many features. That's the beauty of Yeoman! So, to contribute, build another subgenerator - either a 'core' generator or a 'module' generator. All the 'core' generators essentially become like the typical 'forks' - a user will decide what core (s)he wants to use and THEN what modules to include with that core.
    • core: see the core-default folder/generator for an example
    • module: see the ng-route folder/generator for an example
  • NOTE: You will still have to fork the project to develop / contribute; but the point is that we should be able to pull-request all forks into the main fork (assuming code quality of course) so shouldn't need any forks that aren't just being used for development. With ONE source of truth and ONE 'production' fork, we should be able to keep everything in sync and up to date rather than changes in one fork not being supported in all other forks.
  • NOTE: this is still a new idea/approach to contributing and is a work in progress - suggestions welcome! Or if you just think this is a stupid idea feel free to let us know that too - though constructive criticism is always appreciated ;)