René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Replace System.register bundle with a CJS bundle","articleBody":"Most developer workflows are based around CJS (Browserify or WebPack) and not System.js. Since System.js can consume cjs bundles, I suggest we replace our System.register bundle with a CJS bundle. In this case, developers that use Browserify or WebPack will be able to use it, and it should still work with System.\n\nNotes:\n- System.register has a lot of overhead comparing to CJS. My naive measurements showed the difference is about 18%. \n- When using a CJS bundle, you cannot important submodudles, only \"angular2/angular2\". I think this is an advantage cause it prevents users from depending on private API.\n\nFinally, once we produce a CJS bundle, I think we should change our Getting Started guide to use WebPack instead of System.js. The reason is WebPack provides a lot better experience out of the box (including TypeScript and Babel). \n\nThe WebPack config for an Angular 2 project written with TypeScript is about 10 lines long:\n\n```\nmodule.exports = {\n  resolve: {\n    root: __dirname,\n    extensions: ['.ts', '.js']\n  },\n  entry: [\"webpackapp\"],\n  output: {filename: \"webappapp_bundle.js\"},\n  externals: {'angular2/angular2': \"angular2\"},\n  devtool: 'source-map',\n  module: {\n    loaders: [\n      { test: /\\.ts$/, loader: 'ts-loader' }\n    ]\n  }\n}\n```\n\nYou get source maps, dev server with live reload, production/dev modes -- a very good first impression and a clear path to production setting.\n\n/cc @IgorMinar @mhevery @rkirov @jeffbcross \n","author":{"url":"https://github.com/vsavkin","@type":"Person","name":"vsavkin"},"datePublished":"2015-09-21T01:11:28.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":35},"url":"https://github.com/4278/angular/issues/4278"}