To start with the current SFX bundle (angular2.sfx.dev):

• contains the following barrels: zone, reflect-metadata, common, core, instrumentation, platform/browser, upgrade, http, router:
  • common, core, instrumentation, platform/browser are exported on the ng namespace
  • http is exported on the ngHttp namespace
  • router is exported on the ngRouter namespace
• is using dev output
• isn't minified
• doesn't have source maps
• provides support for noConflict mode -> although it is broken now since it doesn't restore ngHttp and ngRouter namespaces

As part of our bundling discussion(s) we've been several times touching upon role, content and setup of the SFX bundle. More specifically the open questions were / are:

• who is the main consumer of the SFX bundle (ES5, ngUpgrade?). AFAIK @rkirov is aware of another use-case
• shell we use the same bundle for ES5 and ngUpgrade scenarios?
• what should be the content? Some barrels are non-controversial (common, core, instrumentation, platform/browser) other are disputable
• what exact namespaces shell be used to export different barrels?
• should we keep the non-conflict mode?

From the list above we can see that there are number of small decisions that we need to take.