Ember.js is a JavaScript framework that does all of the heavy lifting that you'd normally have to do by hand. There are tasks that are common to every web app; Ember.js does those things for you, so you can focus on building killer features and UI.
- Ensure that Node.js and bower are installed.
- Run
git clone https://github.com/emberjs/ember.js.git && cd ember.js
. - Run
git config core.symlinks true
to ensure that symlinks are enabled. - Run
git reset --hard HEAD
to reset to HEAD with symlinks. - Run
npm install
to ensure the required dependencies are installed. - Run
bower install
to ensure required web dependencies are installed. - Run
npm run build
to build Ember.js. The builds will be placed in thedist/
directory.
If you encounter a problem with downloading dependencies like:
npm ERR! registry error parsing json
consider upgrading npm
with:
npm install -g npm@latest
You can find more information in Upgrading on *nix (OSX, Linux, etc.) npm wiki page.
See CONTRIBUTING.md
Pull requests should pass the Ember.js unit tests. Do the following to run these tests.
-
Follow the setup steps listed above under Building Ember.js.
-
To start the development server, run
npm start
. -
To run all tests, visit http://localhost:4200/.
-
To test a specific package, visit
http://localhost:4200/tests/index.html?package=PACKAGE_NAME
. ReplacePACKAGE_NAME
with the name of the package you want to test. For example:
To test multiple packages, you can separate them with commas.
You can also pass jquery=VERSION
in the test URL to test different
versions of jQuery.
-
Install phantomjs from http://phantomjs.org.
-
Run
npm test
to run a basic test suite or runTEST_SUITE=all npm test
to run a more comprehensive suite.
ember test --server
- connect the browsers you want
- if phantom didn't connect automatically, you can run
./bin/connect-phantom-to <optional-port>
To run a specific browser, you can use the --launch
flag
ember test --server --launch SL_Firefox_Current
ember test --launch SL_Firefox_Current