angular-cn/modules_dart
vsavkin 2c8fcec432 refactor(core): move render/dom from core
Currently, core depends on DomRenderer, which depends on the browser.
This means that if you depend on angular2/core, you will always
pull in the browser dom adapter and the browser render, regardless
if you need them or not.

This PR moves the browser dom adapter and the browser renderer out of core.

BREAKING CHANGE

If you import browser adapter or dom renderer directly (not via angular2/core),
you will have to change the import path.
2015-11-17 15:53:55 -08:00
..
transform refactor(core): move render/dom from core 2015-11-17 15:53:55 -08: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.