honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
350 Commits 5 Branches 1 Tag 210 MiB
TypeScript 68.6%
HTML 12.8%
JavaScript 8.4%
Pug 7%
Starlark 1.4%
Other 1.7%
Go to file
Tobias Bosch d02c0accbb refactor(benchmarks): add cloud reporter, add params 
- adds console and cloud reporter (via Google BigQuery).
- makes parameters of tests explicit and modifiable.
- removes `detect` and `ignoreGc` mode from benchpress
  as these can result in unstable numbers.
 		2015-01-15 09:09:05 -08:00
docs chore(docs): module paths must have explicit .js extension 2015-01-09 11:41:01 +00:00
modules refactor(benchmarks): add cloud reporter, add params 2015-01-15 09:09:05 -08:00
scripts feat(test): add e2e tests for benchmarks and examples 2015-01-08 10:51:08 -08:00
tools refactor(benchmarks): add cloud reporter, add params 2015-01-15 09:09:05 -08:00
.gitattributes chore: add .gitattributes with new lines config 2015-01-06 18:06:13 -08:00
.gitignore refactor(benchmarks): add cloud reporter, add params 2015-01-15 09:09:05 -08:00
.travis.yml refactor(perf): use webdriver to execute benchmarks 2014-12-23 22:22:55 -08:00
LICENSE Initial commit 2014-09-18 09:12:01 -07:00
README.md docs(README): missing project name 2015-01-06 18:08:35 -08:00
gulpfile.js refactor(benchmarks): add cloud reporter, add params 2015-01-15 09:09:05 -08:00
karma-dart.conf.js feat(ng-repeat): initial implementaion of ng-repeat. 2014-12-11 11:23:02 -08:00
karma-js.conf.js feat(test): add e2e tests for benchmarks and examples 2015-01-08 10:51:08 -08:00
karma.conf.js chore(karma): add karma.conf.js symlink 2014-11-05 11:19:02 -08:00
package.json refactor(benchmarks): add cloud reporter, add params 2015-01-15 09:09:05 -08:00
perf-cloud-secret.template.js refactor(benchmarks): add cloud reporter, add params 2015-01-15 09:09:05 -08:00
protractor-e2e-dart2js.conf.js feat(test): add e2e tests for benchmarks and examples 2015-01-08 10:51:08 -08:00
protractor-e2e-js.conf.js feat(test): add e2e tests for benchmarks and examples 2015-01-08 10:51:08 -08:00
protractor-e2e-shared.js feat(test): add e2e tests for benchmarks and examples 2015-01-08 10:51:08 -08:00
protractor-perf-dart2js.conf.js refactor(perf): use webdriver to execute benchmarks 2014-12-23 22:22:55 -08:00
protractor-perf-js.conf.js refactor(perf): use webdriver to execute benchmarks 2014-12-23 22:22:55 -08:00
protractor-perf-shared.js refactor(benchmarks): add cloud reporter, add params 2015-01-15 09:09:05 -08:00
pubspec.yaml refactor(build): simplify and modularize 2014-12-05 16:30:36 -08:00
test-main.dart refactor: simplify and make tests work in JS and Dart 2014-09-28 21:50:38 -07:00
test-main.js feat(ng-repeat): initial implementaion of ng-repeat. 2014-12-11 11:23:02 -08:00
traceur-runtime-patch.js feat(deps): update Traceur 0.0.74 2014-11-07 10:29:48 -08:00

README.md

Angular Build Status

Build

Prerequisites:

  1. npm install
  2. npm install -g gulp karma karma-cli
  3. npm install -g protractor
  4. webdriver-manager update
  5. Optionally install Dart SDK (only if you plan on building Dart applications)
  6. Install the Dart SDK
  7. Add the Dart SDK's bin directory to your system path
  8. gulp build
  9. pub get

Folder structure

  • modules/*: modules that will be loaded in the browser
  • tools/*: tools that are needed to build Angular

File endings

  • *.js: javascript files that get transpiled to Dart and EcmaScript 5
  • *.es6: javascript files that get transpiled only to EcmaScript 5
  • *.es5: javascript files that don't get transpiled
  • *.dart: dart files that don't get transpiled

Build:

  1. gulp build -> result is in dist folder
  • will also run pub get for the subfolders in modules and run dartanalyzer for every file that matches <module>/src/<module>.dart, e.g. di/src/di.dart
  1. gulp clean -> cleans the dist folder

Unit tests:

  1. karma start karma-js.conf.js: JS tests
  2. karma start karma-dart.conf.js: Dart tests

Notes for transpiler tests:

The karma preprocessor is setup in a way so that after every test run the transpiler is reloaded. With that it is possible to make changes to the preprocessor and run the tests without exiting karma (just touch a test file that you would like to run).

Performance tests

  1. gulp build.cjs (builds benchpress and tests into dist/cjs folder)
  2. protractor protractor-perf-js.conf.js: JS performance tests
  3. protractor protractor-perf-dart2js.conf.js: Dart2JS performance tests

Examples:

To see the examples, first build the project as described above.

Hello World Example

This example consists of three basic pieces - a component, a decorator and a service. They are all constructed via injection. For more information see the comments in the source modules/examples/src/hello_world/index.js.

You can build this example as either JS or Dart app:

  • (JS) gulp serve.js.dev and open localhost:8000/examples/web/hello_world/ in Chrome.
  • (Dart) gulp serve/examples.dart and open localhost:8080 in Chrome(for dart2js) or dartium(for dart vm).

Debug the transpiler

If you need to debug the transpiler:

  • add a debugger; statement in the transpiler code,
  • from the root folder, execute node debug node_modules/.bin/gulp build to enter the node debugger
  • press "c" to execute the program until you reach the debugger; statement,
  • you can then type "repl" to enter the REPL and inspect variables in the context.

See the Node.js manual for more information.

Notes:

  • You can also execute node node_modules/.bin/karma start karma-dart.conf.js depending on which code you want to debug (the former will process the "modules" folder while the later processes the transpiler specs),
  • You can also add debugger; statements in the specs (JavaScript). The execution will halt when the developer tools are opened in the browser running Karma.

Debug the tests

If you need to debug the tests:

  • add a debugger; statement to the test you want to debug (oe the source code),
  • execute karma node_modules/karma/bin/karma start karma-js.conf.js,
  • press the top right "DEBUG" button,
  • open the dev tools and press F5,
  • the execution halt at the debugger; statement

Note (WebStorm users): You can create a Karma run config from WebStorm. Then in the "Run" menu, press "Debug 'karma-js.conf.js'", WebStorm will stop in the generated code on the debugger; statement. You can then step into the code and add watches. The debugger; statement is needed because WebStorm will stop in a transpiled file. Breakpoints in the original source files are not supported at the moment.