build(docs-infra): update @angular/cli 9.0.0-rc.0 and @angular/* to 9.0.0-rc.1

[gkalpak]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.io application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

[mary-poppins]

You can preview 13acb2e at https://pr33547-13acb2e.ngbuilds.io/.

[mary-poppins]

You can preview 406fbf7 at https://pr33547-406fbf7.ngbuilds.io/.

[mary-poppins]

You can preview 85a8aa5 at https://pr33547-85a8aa5.ngbuilds.io/.

[filipesilva]

Wanna try using --experimentalRollupPass? 😉

[petebacondarwin]

3k greater :-/

[gkalpak]

Added another commit to update @angular/* to 9.0.0-rc.1. PTAL.

[mary-poppins]

You can preview e12873f at https://pr33547-e12873f.ngbuilds.io/.

[gkalpak]

@filipesilva, I tried --experimentalRollupPass, but I am getting the following error (and don't have time to look into it right now):

ERROR in ./src/search.service-f862c759.js
Module not found: Error: Can't resolve './search.worker' in '...\angular\aio\src'
resolve './search.worker' in '...\angular\aio\src'
  using description file: ...\angular\aio\package.json (relative path: ./src)
    Field 'browser' doesn't contain a valid alias configuration
    using description file: ...\angular\aio\package.json (relative path: ./src/search.worker)
      no extension
        Field 'browser' doesn't contain a valid alias configuration
        ...\angular\aio\src\search.worker doesn't exist
      .ts
        Field 'browser' doesn't contain a valid alias configuration
        ...\angular\aio\src\search.worker.ts doesn't exist
      .tsx
        Field 'browser' doesn't contain a valid alias configuration
        ...\angular\aio\src\search.worker.tsx doesn't exist
      .mjs
        Field 'browser' doesn't contain a valid alias configuration
        ...\angular\aio\src\search.worker.mjs doesn't exist
      .js
        Field 'browser' doesn't contain a valid alias configuration
        ...\angular\aio\src\search.worker.js doesn't exist
      as directory
        ...\angular\aio\src\search.worker doesn't exist
[...\angular\aio\src\search.worker]
[...\angular\aio\src\search.worker.ts]
[...\angular\aio\src\search.worker.tsx]
[...\angular\aio\src\search.worker.mjs]
[...\angular\aio\src\search.worker.js]
 @ ./src/search.service-f862c759.js 1:0-143
 @ ./src/main.ts
 @ multi ./src/main.ts

[filipesilva]

@gkalpak these are the needed changes to make the option work: #33096

[gkalpak]

FYI:
With --experimentalRollupPass, the main bundle drops from 464973B to 449612B.
The total size of the lazy modules seems to be going up significantly (120086B -> 192837B ?), although it is hard to tell with the unnamed chunks.

[filipesilva]

I expected a better improvement, will have to look into it,.

[IgorMinar]

@gkalpak could you please test if this regression is coming from CLI changes or fw changes by reverting the cli update?

we should let this PR merge as is, but it would be good to know where the size regression came from.

[gkalpak]

I confirmed the size increase is caused by framework. (I got the exact same number after reverting the CLI update.)

Note that similar size regressions have been seen in integration projects recently (tracked in FW-1665). Not sure they are related, but I wouldn't be surprised 😃

[filipesilva]

At the CLI we also saw it in angular/angular-cli#16099, added potential causes there.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}