angular-cn/pubspec.yaml

name: angular
environment:
  sdk: '>=1.4.0'
dependencies:
  examples:
    path: build/dart/examples
  test_lib:
    path: build/dart/test_lib
  facade:
    path: build/dart/facade
  core:
    path: build/dart/core
  di:
    path: build/dart/di
  change_detection:
    path: build/dart/change_detection

dev_dependencies:
  guinness: ">=0.1.5 <0.2.0"
build - refactor 2014-09-18 17:56:38 -04:00			`name: angular`
			`environment:`
			`sdk: '>=1.4.0'`
			`dependencies:`
chore(build): execute `pub get` only if a pubspec.yaml changed and run `dart analyzer` on all dart files `pub get` is now only executed when the `pubspec.yaml` in the `modules` folder is different than the `pubspec.yaml` in the `build/dart` folder. Generates the file `build/dart/_analyzer.dart` that imports all modules to run `dart analyzer` against all of them. The build will fail whenever there are errors, warnings or hints in `dart analyzer`. Changes the sources so that `dart analyzer` does not report any error, warning or hint. Closes #40 2014-10-02 15:27:01 -04:00			`examples:`
			`path: build/dart/examples`
chore: karma with JS, Dart Note: karma with dart is still not working because of how `karma-dart` loads `package:…` dependencies. Usage: ``` karma start karma-js.conf.js karma start karma-dart.conf.js ``` Make sure to set `DARTIUM_BIN` env variable. Refactors `js2dart`: - live outside of the traceur module (`tools/js2dart/index.js`) so it can be reused by gulp and karma - automatically build the sources in memory, so that `js2dart` can be used without running `gulp build` first - provide a way to specify the moduleName of a compilation run independently of the input filename. This helps error messages and source maps (not yet enabled) to report the correct file name Changes project setup: - add module `test_lib` that contains the primitives for tests (e.g. `describe`, `it`, …) - clean up some sources that had errors in them - module names in transpiled js and dart files don’t contain `lib`, `test` nor `src` any more (e.g. `di/di`). 2014-09-25 17:04:46 -04:00			`test_lib:`
refactor: simplify and make tests work in JS and Dart * remove `wraps` syntax enhancements for imports and support new `import * as module from ...` syntax - default imports are the wrong construct for importing everything from a module * moved tests from transpiler to jasmine and karma - transpiler tests are included when running karma in main project folder - transpiler is reloaded after every test run in karma, so no need to restart karma when the transpiler has been changed. - removed own gulp build for transpiler and `postinstall.sh` as they are no more needed. - transpiler tests are now executed in Dart AND JavaScript (used to be executed only in Dart), which allowed to catch some bugs (see the bug with the import specification above). * made tests work in dart as well by using the following hack: - dependencies are loaded from the `build` folder, which makes running `gulp build` necessary before running karma for dart - for this to work, the dependencies are included in main `pubspec.yaml` of project - reason for the hack: `karma-dart` loads all `packages` urls directly from disc (should rather use the karma file list) * added explicit annotations `FIELD`, `ABSTRACT`, ... to `facade/lang.` - needed for now that we can run tests and don't get errors for undefined annotations. added `README.md` with details about the build and tests 2014-09-28 16:55:01 -04:00			`path: build/dart/test_lib`
			`facade:`
			`path: build/dart/facade`
			`core:`
			`path: build/dart/core`
			`di:`
			`path: build/dart/di`
			`change_detection:`
			`path: build/dart/change_detection`

			`dev_dependencies:`
chore: karma with JS, Dart Note: karma with dart is still not working because of how `karma-dart` loads `package:…` dependencies. Usage: ``` karma start karma-js.conf.js karma start karma-dart.conf.js ``` Make sure to set `DARTIUM_BIN` env variable. Refactors `js2dart`: - live outside of the traceur module (`tools/js2dart/index.js`) so it can be reused by gulp and karma - automatically build the sources in memory, so that `js2dart` can be used without running `gulp build` first - provide a way to specify the moduleName of a compilation run independently of the input filename. This helps error messages and source maps (not yet enabled) to report the correct file name Changes project setup: - add module `test_lib` that contains the primitives for tests (e.g. `describe`, `it`, …) - clean up some sources that had errors in them - module names in transpiled js and dart files don’t contain `lib`, `test` nor `src` any more (e.g. `di/di`). 2014-09-25 17:04:46 -04:00			`guinness: ">=0.1.5 <0.2.0"`