Verify that SEO works well with differential loading

I tried to quickly test next.angular.io with https://search.google.com/test/mobile-friendly to ensure that SEO was not being broken, but that didn’t work because of the robots.txt on next.angular.io.

So I deployed the version with 8.0.0-rc.2 (#30202) updates to https://angular-io-v42.firebaseapp.com/ and tested it and got an odd error (results link):

Which seems to be due to some issue with how we transpile the code or load polyfills:

Can someone check what’s up with this and ensure that the SEO works, and ideally works OOB for any ng new project created with 8.0.0 - I think that now that we have the polyfills differentialy loaded there should be no reason for ng new not to be SEO-compatible out of the box (no advanced stuff, just not blow up).

// @petebacondarwin @filipesilva

[JiaLiPassion]

@petebacondarwin, thank you, and I tested it here, https://aio-test-27ab8.firebaseapp.com/, everything works fine. So I will reach @vikerman to make a new release of zone.js.

https://github.com/angular/zone.js/pull/1230 is ready, after it is merged, I will create a PR to update the version of angular repo.

[petebacondarwin]

It looks like the problem is caused by Zone.js 0.9.0. This issue is almost identical… https://github.com/angular/zone.js/issues/1223#issuecomment-486110447

This deployment has the Zone.js downgraded to 0.8.29: https://aio-test-app-for-filipe.firebaseapp.com/ Running the Google indexer on it gives no error: https://search.google.com/test/mobile-friendly?id=x1ComSZAlxd4iU0sPwQxFQ