tsickle is not installed by default in 7.0.0-rc.0

I’m submitting a…

[X] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:

Current behavior

Noticed a breaking change when updating a simple app from 6.1.x to 7.0.0-rc.0 and trying to bundle our applications with closure compiler.

tsickle is not installed when running npm install on typical angular packages.

Expected behavior

tsickle is installed by @angular packages like before.

Minimal reproduction of the problem with instructions

npm install -g @angular/cli@latest angular-rollup@latest ngr new my-app <-- you are generating a new app with ngr instead of ng Update angular packages to 7.0.0-rc.0 and typescript to 3.1.1 ngr build prod --serve Notice in terminal error about tsickle module is missing

: Error: Cannot find module 'tsickle'
    at Function.Module._resolveFilename (module.js:555:15)
    at Function.Module._load (module.js:482:25)
    at Module.require (module.js:604:17)
    at require (internal/module.js:11:18)

npm install tsickle Error is gone.

• NOTE there is separate issue preventing closure compiler from bundling because of new dependence on @angular/compiler in @angular/core package.

If you add below to the closure.conf the build will now work.

--js node_modules/@angular/compiler/package.json
--js node_modules/@angular/compiler/fesm2015/compiler.js

What is the motivation / use case for changing the behavior?

Maintenance of tsickle version is now on application team and is no longer in sync with compiler.

Environment

Angular version: 7.0.0-rc.0


Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: v9.5.0
- Platform:  MacOS

Others:

[steveblue]

OK, but now tsickle is not a dependency of @angular/compiler-cli how are teams using tsickle supposed to know which version of tsickle is directly compatible with @angular other than being on the latest version of both packages? If a user facing angularCompilerOption triggers tsickle why shouldn’t it work out of the box? This seems like it will be very confusing for noobs.

[StephenFluin]

@alexeagle is looking at the right resolution, because for most developers tsickle is optional.