85b5543f62 | ||
---|---|---|
modules | ||
scripts | ||
tools/transpiler | ||
.gitignore | ||
.travis.yml | ||
LICENSE | ||
README.md | ||
TODO.md | ||
file2modulename.js | ||
gulpfile.js | ||
karma-dart.conf.js | ||
karma-js.conf.js | ||
package.json | ||
pubspec.yaml | ||
test-main.dart | ||
test-main.js |
README.md
Build
Prerequisites:
npm install
pub get
install -g gulp
install -g karma
Folder structure
modules/*
: modules that will be loaded in the browsertools/*
: 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:
gulp build
-> result is inbuild
folder
- will also to
pubg get
for the subfolders inmodules
and rundartanalyzer
for every file that matches<module>/src/<module>.dart
, e.g.di/src/di.dart
gulp clean
-> cleans thebuild
folder
Tests:
karma start karma-js.conf.js
: JS testskarma start karma-dart.conf.js
: JS 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 thebuild
folder for resolvingpackage:
dependencies (created e.g. forimport ... from 'di:di'
). So you need to executegulp build
before this.