TL;DR skip to the table at the bottom to see how I'm suggesting we move things around

Partial Backlog Based on Proposal and Discussion

Done

• refactor(http): move http into its own module as sibling of angular2 #2680 @jeffbcross refactor(http): move http into its own module as sibling of angular2
• fix(typings): typings template should make module name at end of file dynamic #2948 @jeffbcross fix(typings): typings template should make module name at end of file dynamic
• feat(typings): bundle typings should be able to declare references #3540 @jeffbcross feat(typings): bundle typings should be able to declare references
• feat(package): add "typescript" field with typings information #3590 @jeffbcross feat(package): add "typescript" field with typings information
• feat(bundles): include all bundles in npm distributions #3555 feat(bundles): include all bundles in npm distributions
• cancelled refactor(di): move di into its own top-level module #3416 refactor(di): move di into its own top-level module
• cancelled refactor(facade): move facade into separate top-level module #3415 refactor(facade): move facade into separate top-level module
• cancelled feat(dist): include "core" modules in angular2 npm dist #3588 feat(dist): include "core" modules in angular2 npm dist

In-Progress

• chore: re-arrange sources to better reflect npm package and import paths #3713 @jeffbcross chore: re-arrange sources to better reflect npm package and import paths
• chore: change bundle rules to generate one sfx module and several minimal modules #3714 @jeffbcross chore: change bundle rules to generate one sfx module and several minimal modules

Unscheduled

• export type definitions for test_lib #3423 export type definitions for test_lib
• docs: API reference should also include global/ambient object names included in sfx bundles #3651 docs: API reference should also include global/ambient object names included in sfx bundles
• chore(zone): add zone.js to bundles and npm distribution #3712 chore(zone): add zone.js to bundles and npm distribution

Goals

• Simple, predictable, consistent package installation and consumption experience for end-users
• Have minimal, logical bundles for production use (router bundle, core bundle, http bundle, full bundle with deps, etc)
• Pave path toward eventually being able to separate modules into separate repositories with independent development lifecycles
• Maximum symmetry between Dart and JavaScript publishing (naming and structure mostly)
• Logical import and require paths for end users, without having to think about hierarchy or relationships of modules (import {Http} from 'angular/http' or require('angular/router'))

Use Cases

• User wants to create a quick code sample on plunker
• User wants to create a production app with no build process but reasonable byte size
• User wants to create a production app with a proprietary build process that creates minified bundles
• User wants to create a production app on HTTP/2 server, using SystemJS loader, with no bundles, but minified modules that are loaded when needed.

Characteristics of Modules

• Is likely to be used outside of an angular app, without a dependency on Angular?
• Is it a runtime requirement of angular2?
• Is useful as a runtime utility for third-party Angular libraries?
• Is it primarily a tool, not useful in an app at runtime?

Proposal

• If it is not Required and not Tooling, it becomes a subdirectory of modules/angular2/ and gets its own bundle.
• If it is not Required, it should be moved to the top-level of the angular2/modules directory,
  , i.e. angular2/modules/http
• All bundles will be pushed to code.angularjs.org
• All runtime modules that are currently part of the core repo should be published inside of the angular2 package on NPM and Pub (zone.js should also be added to the npm dist).

* Primary import namespaces when used in the context of an angular 2 app, as opposed to being used independently of Angular.
For example: import {FORM_DIRECTIVES} from 'angular2/forms';.
** No bundle because only used in nodejs environment.

Bundles

These will be the bundles that are exported:

• angular2.js (includes all other bundles)
• core.js
• forms.js
• http.js
• router.js
• web-worker.js
• zone.js

And these are the extensions with which each bundle will be published to code.angularjs.org and npm. Bundles will be in the bundles folder of the npm package and will be published to code.angularjs.org as code.angularjs.org/<version-number>/<bundle-name>.

• .js
• .d.ts (typings are in separate typings folder in npm distribution)
• .js.map
• .min.js (Using uglify for now, eventually using angular/ts-minify)
• .dev.js (runs in dev mode)
• .dev.js.map
• -testing.js
• -testing.js.map
• -testing.d.ts

The angular2 bundle will also get an sfx version, which will include dependencies like Rx, reflect-metadata, traceur-runtime, and will export a global ng object.

• angular2.sfx.js
• angular2.sfx.min.js
• angular2.sfx.js.map
• angular2.sfx.min.js.map

The -testing bundles will include testing utilities and mocks for the respective module. The core-testing.js will include the bulk of the testing utilities, leaving other testing bundles to mostly just include mocks.