History

Misko Hevery ea6673947c refactor: rename annotations to metadata BREAKING CHANGE (maybe) Well as long as our customers use public API this should not be a breaking change, but we have changed import structure as well as internal names, so it could be breaking. import: angular2/annotations => angular2/metadata Classes: Annotations => Metadata renderer.DirectiveMetadata => renderer.RendererDirectiveMetadata renderer.ElementBinder => renderer.RendererElementBinder impl.Directive => impl.DirectiveMetadata impl.Component => impl.ComponentMetadata impl.View => impl.ViewMetadata Closes #3660		2015-08-17 21:23:25 +00:00
..
analysis_server	chore(sources): intro modules_dart; move analyzer code there	2015-04-24 13:29:18 -07:00
analyzer_plugin	refactor: rename annotations to metadata	2015-08-17 21:23:25 +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

Run gulp build.dart
Open the package in any Dart IDE of your choice
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

Create a new directory with its own pubspec.yaml and standard pub layout.
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.