Explain the webpack setup about mfe-starter

[PatrickJS]

I'm using ./src/common/BrowserDomAdapter to ensure that the script being compile is using the correct dom adapter (I had a problem in the past where this was a problem in webpack). And the other files are not needed

[PatrickJS]

I removed everything except angular2/angular2
https://github.com/angular-class/angular2-webpack-starter/blob/master/webpack.config.js

    'angular2': [
      // Angular 2 Deps
      'zone.js',
      'reflect-metadata',
      'rtts_assert/rtts_assert',
      'angular2/angular2'
    ],

[gajus]

I nonetheless do not understand the reason you are including angular2/angular2. Your entry point is your app script. It imports angular2/angular2 using import statement. Unless I am missing something, if you are including angular2/angular2 this way, your script does not even pick it up, i.e. dead weight.

On Jul 19, 2015, at 16:16, PatrickJS [email protected] wrote:

I removed everything except angular2/angular2
https://github.com/angular-class/angular2-webpack-starter/blob/master/webpack.config.js

'angular2': [
  // Angular 2 Deps
  'zone.js',
  'reflect-metadata',
  'rtts_assert/rtts_assert',
  'angular2/angular2'
],

—
Reply to this email directly or view it on GitHub.

[PatrickJS]

When webpack generates the file it chunks modules together so I'm forcing Angular to remain in one file for the browser to cache.

[gajus]

Thats because you are using the plugin. This kinda defeats the purpose of the latter plugin, esp. on a small app.

On Jul 19, 2015, at 18:00, PatrickJS [email protected] wrote:

When webpack generates the file it chunks modules together so I'm forcing Angular to remain in one file for the browser to cache.

—
Reply to this email directly or view it on GitHub.