iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
141 Commits 5 Branches 1 Tag 142 MiB
TypeScript 68.6%
HTML 12.8%
JavaScript 8.4%
Pug 7%
Starlark 1.4%
Other 1.7%
Go to file
Vojta Jina 9dd7cae9fd chore(travis): fix the build 
I don’t know what the issue really is. There is some weird race condition,
where the task copies the file (`pubspec.yml`) and then start `pub get`
which reads that file and the file is not there or is empty.

I have no idea why moving this task into a separate process fixes the
issue but I don’t wanna waste more time on it.
 		2014-11-05 11:19:03 -08:00
modules fix(example): make it work 2014-11-05 11:19:02 -08:00
scripts chore(travis): fix the build 2014-11-05 11:19:03 -08:00
tools/transpiler chore: source maps for Karma/Gulp 2014-11-05 11:19:02 -08:00
.gitignore feat(benchmark): add a simple benchmark for the di module 2014-10-18 17:06:23 -04:00
.travis.yml chore(travis): cleanup travis.yml 2014-10-28 11:51:00 +01:00
LICENSE Initial commit 2014-09-18 09:12:01 -07:00
README.md doc(debug): add instructions for debugging the tests in the README 2014-10-30 09:58:23 +01:00
TODO.md refactor: simplify and make tests work in JS and Dart 2014-09-28 21:50:38 -07:00
file2modulename.js transpiler: normalize Dart library name 2014-10-07 17:35:22 -07:00
gulpfile.js chore: fix modules/build.dart/pubspec 2014-11-05 11:19:02 -08:00
karma-dart.conf.js chore: source maps for Karma/Gulp 2014-11-05 11:19:02 -08:00
karma-js.conf.js chore: source maps for Karma/Gulp 2014-11-05 11:19:02 -08:00
karma.conf.js chore(karma): add karma.conf.js symlink 2014-11-05 11:19:02 -08:00
package.json chore: fix modules/build.dart/pubspec 2014-11-05 11:19:02 -08:00
pubspec.yaml feat(test_lib): change test_lib.dart to structurally compare objects 2014-10-29 18:25:32 -04: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 chore: use es6-module-loader 2014-10-07 17:35:22 -07:00

README.md

Build Status

Build

Prerequisites:

  1. npm install
  2. npm install -g gulp karma karma-cli
  3. Install the Dart SDK
  4. Add the Dart SDK's bin directory to your system path
  5. gulp build
  6. 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 build 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 build folder

Tests:

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

Notes for all 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).

Restriction for Dart tests (for now):

  • Due to a bug karma-dart plugin, this will use the files in the build folder for resolving package: dependencies (created e.g. for import ... from 'di:di'). So you need to execute gulp build before this.

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.