This is a
playground to test code. It runs a full
Node.js environment and already has all of
npm’s 400,000 packages pre-installed, including
generator-ember-jade-zurb with all
npm packages installed. Try it out:
This service is provided by RunKit and is not affiliated with npm, Inc or the package authors.
Maintainer: Anthony Bull
The scaffolding tool for Ember.js apps.
npm install -g grunt-contrib-compass
You should have one path each for:
which ruby && which compass
npm install -g generator-ember-jade-zurb
mkdir webapp && cd webapp
npm install -g grunt-mocha
A welcome page should appear in your browser.
Creates a model, views, handlebars, controllers, view/edit routes, and some basic fixtures given an arg, as in:
yo ember:model User name:string zipcode:number
Creates a view and template given an arg, as in
yo ember:view Foo
KNOWN ISSUE: IF YOU ADD A NEW VIEW, REGARDLESS OF WITH WHICH GENERATOR, YOU HAVE TO RESTART THE SERVER.
Creates a view, handlebar, controller and route given an arg, as in:
yo ember:controller Bar
(and updates router.js, overwrite when prompted)
Skips the automatic execution of
npm after scaffolding has finished.
mocha. Can be switched for another supported testing framework like
Enable support for CoffeeScript.
Enables support for karma test runner
Testing your app is as simple as running
grunt test. The generator ships with the
karma test runner for running the tests. Integration
tests are written with ember-testing
and preferably mocha. Karma is highly configurable and you can take a look at the varity of options
on its website.
-bash: yo: command not found
You need to make sure that npm is on your path. Add the following to your .bash_profile (or .bashrc):
You specified the templateName ... but it did not exist.
You probably added a view; restart the server.
See the changelog file
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 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.
Here are some of the techniques I use; maybe they're useful for you.
npm linkto use what's in the local repo for
cd .. && rm -rf webapp) from time-to-time to ensure the code output is coming from the latest generator (will re-install everything via npm, so be forewarned)