angular-cn/modules/angular2/angular2.ts

export * from './common';
export * from './core';
export * from './instrumentation';
export * from './platform/browser';
export * from './src/platform/dom/dom_adapter';
export * from './src/platform/dom/events/event_manager';
export * from './upgrade';
export {UrlResolver, AppRootUrl} from './compiler';
feat(core): add support for ambient directives Ambient directives can be configured when bootstraping an application. Ambient directives can be used in every component of the application without needing to explicitly list them. 2015-11-02 19:03:42 -05:00			`export * from './common';`
chore(API): cleaned up top level imports (render) 2015-07-24 17:56:57 -04:00			`export * from './core';`
cleanup(tooling): move tooling to the browser platform and rename profile into instrumentation BREAKING CHANGE Before import * as p from 'angular2/profile'; import * as t from 'angular2/tools'; After import * as p from 'angular2/instrumentation'; import * as t from 'angular2/platform/browser'; 2015-11-23 13:18:04 -05:00			`export * from './instrumentation';`
feat(core): extract platforms out of core Currently, core depends on the browser, which means that other platforms (e.g., NativeScript or webworker) cannot use the bootstrapping logic core provides. This PR extract makes bootstrapping logic in core completely platform-independent. The browser-specific code was moved to "angular2/platforms/browser". BREAKING CHANGE A few private helpers (e.g., platformCommon or applicationCommon) were removed or replaced with other helpers. Look at PLATFORM_COMMON_PROVIDERS, APPLICATION_COMMON_PROVIDERS, BROWSER_PROVIDERS, BROWSER_APP_PROVIDERS to see if they export the providers you need. Closes #5219 Closes #5280 2015-11-13 14:21:16 -05:00			`export * from './platform/browser';`
cleanup: move DomAdapter from angular2/core into angular2/platform/common_dom BREAKING CHANGE Before import {DomAdapter} from 'angular2/core'; After import {DomAdapter} from 'angular2/platform/common_dom'; Closes #5370 2015-11-19 18:09:34 -05:00			`export * from './src/platform/dom/dom_adapter';`
refactor(core): move EventManager from core to platform/dom Closes #5465 2015-11-24 18:05:04 -05:00			`export * from './src/platform/dom/events/event_manager';`
chore(ngUpgrade): Move into Angular2 This is moving ngUpgrade into the main repository per #4838. The ngUpgrade is published from the main import consistent with https://docs.google.com/document/d/1rbVTKTYLz6p2smQNYI8h4-QN-m2PS6F3iQIDmSzn0Ww/edit#heading=h.6cxvr9awtf5r Closes #4931 2015-10-26 23:17:46 -04:00			`export * from './upgrade';`
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 18:24:36 -05:00			`export {UrlResolver, AppRootUrl} from './compiler';`