-
Notifications
You must be signed in to change notification settings - Fork 12k
Regression with ancient Chrome/Chromium after update to v8.0 #14618
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Facing same issue after upgrading by following steps from https://update.angular.io/#7.0:8.0 ng update @angular/cli @angular/core PhantomJS 2.1.1 (Windows 7.0.0) -- here is my current polyfills.ts -- import 'core-js/es6/symbol'; |
Hi, on using promise in angular-ui-router, I am getting the same error. Google Chrome is up to date |
I've got something like this as well from my On a brand new project, (e.g.
Now,
This looked to me like a problem with which version of JS being used, so in my Now,
Ok, still having some problems with the Javascript. So let's try adding in all the core-js polyfills that got removed a while ago (but are somehow still necessary for anything to work right).
And then in
Now,
And this message is similar, though not exactly the same message OP is dealing with. I'm wondering if, for whatever reason, both these headless browsers are somehow trying to load both the es5 and es2015 bundles - and so one bundle overwrites ZoneAwarePromise, but it's basically with the same thing. The tests continue to run, but they each emit this message. |
The same error @thecp described can be observed with PhantomJs
|
Hi, indeed this is an issue and we have a fix for this #14693 It’s paramount to mention that one should not add the above mentioned core-js polyfills in their polyfills.ts file as that would add the polyfills twice. core-js polyfills are already added internally during the build https://github.com/angular/angular-cli/blob/master/packages/angular_devkit/build_angular/src/angular-cli-files/models/es5-jit-polyfills.js |
Thanks for the help, @alan-agius4
Something must be going awry in the build process then because I need to add all of those polyfills otherwise, I get all kinds of error messages in IE11. I had to do this in 7.0 as well. I don't think most people these days are even thinking of IE11, but it has twice the marketshare of Edge and gets used by a good portion of our clients. In my particular app, it complains first about Array.prototype.includes being undefined, but more errors are thrown once I've added Maybe my browserslist file is wrong, it looks like this:
|
…TMLs Similar to the index HTML page (https://github.com/angular/angular-cli/blob/6ec09919b5c2695dee784ce0c3accee7f9754bb0/tests/legacy-cli/e2e/tests/misc/support-ie.ts#L30-L37) ES5 polyfills should be loaded prior to the other polyfills. This is because other polyfills such as `zone.js` require these for example `Symbol` and `Object.isFrozen` Fixes #14618
…TMLs Similar to the index HTML page (https://github.com/angular/angular-cli/blob/6ec09919b5c2695dee784ce0c3accee7f9754bb0/tests/legacy-cli/e2e/tests/misc/support-ie.ts#L30-L37) ES5 polyfills should be loaded prior to the other polyfills. This is because other polyfills such as `zone.js` require these for example `Symbol` and `Object.isFrozen` Fixes #14618
@Senneseph, we only add polyfills which are needed by Angular framework itself. Any other polyfills that other dependencies or the application code requires will need to be added by yourself. |
For an IE 11 Angular 8 app: after creating a new angular project using CLI 8.0.3, changed tsconfig.json from "target": "es2015", to "target": "es5" and ng test yielded no errors. However, the title did not render in test, but it does render in IE when I run with ng serve localhost:4200. Test results: after several refreshes my-app2 finally appeared in the h1 tag as Welcome to my-app2!. This happened in Chrome and IE |
@Senneseph I have the same issue you described on my local machine and in our Jenkins build script:
Did you find a fix for this? I have tried:
From reading through this issue trail and reading #14693 I can't find a definitive answer. @alan-agius4 Thanks! |
To fix this issue, be sure you have Then you need to edit This worked for me to have again a working IE11. |
For anyone who's struggling with running PhantomJS tests with Angular 8 locally and/or in a build pipeline, this worked for me:
EDIT: This workaround isn't the best solution either. By changing the target attribute to |
I know this is closed and there's a merge that was supposed to fix it, but I am still unable to get past this error:
Is there anyone who ran into this same issue and successfully resolved it? |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
🐞 Bug report
Command (mark with an
x
)Is this a regression?
Yes, the previous version in which this bug was not present was: 7.2.15. The issue occurred after update to v8.Description
After update from v7.2 to v8 with Chrome (or more precisely Chromium) version 57 (yes, I know...)
ng test
fails for ALL tests and GUI stopped working. While latter I can only reproduce with a bigger app,ng test
already fails for a fresh project withng new
.🔬 Minimal Reproduction
ng new
ng test
with Chromium v57 (on Debian 8)(I created a small repo as a showcase for this: https://github.com/thecp/angular-8-test)
🔥 Exception or Error
🌍 Your Environment
Also most importantly:
Anything else relevant?
Again, only discovered this with Chromium v57 on Debian 8 Jessie
The text was updated successfully, but these errors were encountered: