don't re-bundle zone.js about angular2-seed HOT 5 CLOSED

The problem is that webpack disagrees by bundling angular2-polyfills becaut it says that it is a bundle already and you should link the original sources (zone and reflect).

from angular2-seed.

I understand that this suggestion doesn't quite match WebPack's philosophy. But in this case this philosophy is wrong. And we really don't want to re-package zone.js

We can't tell people "hey, you can't include anything in a script tag since WebPack has a different opinion". What about things like es6-shim? Are we going to force people to bundle it as well?

from angular2-seed.

As long as your solution is not extra script tags, that won't work for building a production build with webpack. Or change the entire webpack.

from angular2-seed.

It is not re-bundled any more which is good. But it is still not loaded via a script tag, which is bad. Will open a separate issue for this.

from angular2-seed.

crypto is being imported because of the way reflect-metadata is handling the polyfill. To ensure that webpack doesn't polyfill the browser environment with node (browserify does the same) we have to noop crypto with

module.exports = {
  node: { crypto: 'empty' }
};

you can see it here https://github.com/angular/angular2-seed/pull/28/files#diff-11e9f7f953edc64ba14b0cc350ae7b9dR30

from angular2-seed.