angular-cn/modules_dart
Tim Blasi 4d0c2ed1f6 test(dart/transform): Update dependencies & fix Dart tests
Widen version dependencies for `package:angular`, `package:code_transformers`,
and `package:observe`.

`package:guinness` uses `package:unittest` while
the newest versions of `package:code_transformers` use `package:test`.
This causes our end-to-end Dart transformer tests (which use testing
code in `package:code_transformers`) to be skipped.

To fix this:
- Move e2e tests to run in a separate file
- Run `gulp test.server.dart` tests serially

Closes #5922

Closes #5935
2016-01-14 00:29:03 +00:00
..
angular2_testing feat(test): allow tests to specify the platform and application providers used 2016-01-13 02:11:06 +00:00
payload/hello_world feature(dart/transform): Inject `initReflector` at @AngularEntrypoint 2015-12-01 13:34:29 -08:00
transform test(dart/transform): Update dependencies & fix Dart tests 2016-01-14 00:29:03 +00:00
README.md docs(modules_dart): add README.md 2015-05-08 13:45:26 -07:00

README.md

This directory contains pure Dart packages that use standard pub layout.

Working with an existing package

  1. Run gulp build.dart
  2. Open the package in any Dart IDE of your choice
  3. Tada!

You do not need to rerun step 1 if you are only making changes in modules_dart. However, you do need to run it again after you make a change in modules. This is because these packages depend on code inside the dist directory via dependency_overrides. Code in modules need to be transpiled into dist before the IDE can "feel" your changes in modules.

Creating a new package

  1. Create a new directory with its own pubspec.yaml and standard pub layout.
  2. Add both a normal dependency on angular2 and a dependency_overrides, like this:
version: 0.0.0
dependencies:
  angular2: '0.0.0'
dependency_overrides:
  angular2:
    path: ../../dist/dart/angular2

The publishing script will automatically rewrite version numbers, so use 0.0.0 both for your package and angular2 version. Similarly, do not include authors and homepage, as they will be auto-populated. However, do provide description, name (prefixed with angular2_), dependencies, and dev_dependencies.