Closed jared83 closed 8 years ago
This project is a generator based in angular-webpack-starter, so problably you should report the issue there.
So I will try to replicate the issue. Can you give more info about your project? It's the code generated and executed or you change/add something?
I changed nothing in the configuration files. None of them. The only things I did are
yo angular2-webpack-starter:component <name>
didn't work properly for me (will report on that too).that is all I did.
It turns out the issue was/is on Angular 2 beta1 side. To fix it I disabled the UglifyJsPlugin in the webpack.prod.config.js file. This issue can now be closed.
Ok, thanks
Hi there, I have created and described my issue in angular2 repo here (issue 6604), but then I thought it could be a problem with the build process rather than with the angular2 itself. So here I go: I am using generator-angular2-webpack-starter To get me up with angular 2. Initially I was suffering from the #6450 issue (and #6516, and #6556), but fixed it with this shim. This made ie11 (ver. 11.0.9600.18161 under win8.1 64bit) run angular 2 without a hitch when served with 'npm run server' i.e. the default server for development. However, when I run the production server ( 'npm run server:prod' ) I am getting this error from ie:
and but a "Loading..." message on the screen. Any help highly appreciated. I've got to get this running in ie asap. Thank you for your time in advance. Jared