Upgrade to 9 breaks ng-universal application.

[shane-arthur]

Angular 9 Upgrade Issues

Our team recently tried to upgrade to Angular 9 RC following the migration guide https://update.angular.io/ upgrading from 8.0x to 9.

When trying to run our universal build we are met with the following errors.

TypeError: Cannot Assign to read only property '_showWarnings' of object '#'

[alan-agius4]

Kindly provide the full output of ng version & also the output of the log file. Parts of it is truncated in the the screenshot.

Thanks.

[kapilpatel20]

I am facing the same issue . Here below is my ng version

[kapilpatel20]

I am using Angular 8 universal and facing the same problem.

[clydin]

Can you provide the output of npm ls webpack from within the project?

[kapilpatel20]

the output is

└─┬ @angular-devkit/build-angular@0.803.19
  └── webpack@4.39.2

[kaushikparmar]

Hey @alan-agius4

@shane-arthur Did you solve this one?

This is the output of the log file.

TypeError: Cannot assign to read only property '_showWarnings' of object '#'
at TapSubscriber._visitJsonRecursive.pipe.operators_1.tap.x [as _tapNext] (/home/fxqa/www/web/node_modules/@angular/cli/node_modules/@angular-devkit/core/src/json/schema/visitor.js:56:210)
at TapSubscriber._next (/home/fxqa/www/web/node_modules/@angular/cli/node_modules/rxjs/internal/operators/tap.js:59:27)
at TapSubscriber.Subscriber.next (/home/fxqa/www/web/node_modules/@angular/cli/node_modules/rxjs/internal/Subscriber.js:66:18)
at MergeMapSubscriber.notifyNext (/home/fxqa/www/web/node_modules/@angular/cli/node_modules/rxjs/internal/operators/mergeMap.js:92:26)
at InnerSubscriber._next (/home/fxqa/www/web/node_modules/@angular/cli/node_modules/rxjs/internal/InnerSubscriber.js:28:21)
at InnerSubscriber.Subscriber.next (/home/fxqa/www/web/node_modules/@angular/cli/node_modules/rxjs/internal/Subscriber.js:66:18)
at /home/fxqa/www/web/node_modules/@angular/cli/node_modules/rxjs/internal/util/subscribeTo.js:17:28
at Object.subscribeToResult (/home/fxqa/www/web/node_modules/@angular/cli/node_modules/rxjs/internal/util/subscribeToResult.js:10:45)
at MergeMapSubscriber._innerSub (/home/fxqa/www/web/node_modules/@angular/cli/node_modules/rxjs/internal/operators/mergeMap.js:82:29)
at MergeMapSubscriber._tryNext (/home/fxqa/www/web/node_modules/@angular/cli/node_modules/rxjs/internal/operators/mergeMap.js:76:14)
at MergeMapSubscriber._next (/home/fxqa/www/web/node_modules/@angular/cli/node_modules/rxjs/internal/operators/mergeMap.js:59:18)
at MergeMapSubscriber.Subscriber.next (/home/fxqa/www/web/node_modules/@angular/cli/node_modules/rxjs/internal/Subscriber.js:66:18)
at Observable._subscribe (/home/fxqa/www/web/node_modules/@angular/cli/node_modules/rxjs/internal/observable/scalar.js:6:20)
at Observable._trySubscribe (/home/fxqa/www/web/node_modules/@angular/cli/node_modules/rxjs/internal/Observable.js:44:25)
at Observable.subscribe (/home/fxqa/www/web/node_modules/@angular/cli/node_modules/rxjs/internal/Observable.js:30:22)
at MergeMapOperator.call (/home/fxqa/www/web/node_modules/@angular/cli/node_modules/rxjs/internal/operators/mergeMap.js:39:23)[fxqa@FX web]$

[kaushikparmar]

@shane-arthur

Me and @kapilpatel20 are able to solve this issue.

The reason behind this is @angular-devkit/build-angular@0.803.19

It was @angular-devkit/build-angular@0.803.5 when we created the Angular Universal project then someone did npm install and it got updated due to ^ symbol.

We reverted the version back to @angular-devkit/build-angular@0.803.5 and it started working properly.

[guiseek]

i have the same problem... works but doesn't allow sequential or concurrent commands for practical builds

[guiseek]

@shane-arthur

Me and @kapilpatel20 able to solve this issue.

The reason behind this is @angular-devkit/build-angular@0.803.19

It was @angular-devkit/build-angular@0.803.5 when we created the Angular Universal project then someone did npm install and it got updated due to ^ symbol.

We the version back to @angular-devkit/build-angular@0.803.5 and it started working properly.

Great!!! thanks bro!

[eternalmatt]

Replying "me too" except I am on angular@8.2.0 after installing a new app from Nx. This only occurs when I build my universal server. Downgrading to 0.803.5 works.

If it matters here are my dependencies, since I seem to be the outlier experiencing the error on 8 and not 9:

{
    "@angular/common": "^8.2.0",
    "@angular/compiler": "^8.2.0",
    "@angular/core": "^8.2.0",
    "@angular/platform-browser": "^8.2.0",
    "@angular/platform-browser-dynamic": "^8.2.0",
    "@angular/platform-server": "^8.2.14",
    "@nguniversal/common": "^8.1.1",
    "@nguniversal/express-engine": "^8.1.1",
    "@nguniversal/module-map-ngfactory-loader": "^8.1.1",
}

[mehrad-rafigh]

We are experiencing the same issue in our team. Downgrading build-angular to 0.803.6 fixed our problem
With 0.803.7 up to the current version - which is 0.803.20 at the time of writing - we get the error, which has been reported in our Universal Builds

[pakman198]

@shane-arthur

Me and @kapilpatel20 are able to solve this issue.

The reason behind this is @angular-devkit/build-angular@0.803.19

It was @angular-devkit/build-angular@0.803.5 when we created the Angular Universal project then someone did npm install and it got updated due to ^ symbol.

We reverted the version back to @angular-devkit/build-angular@0.803.5 and it started working properly.

Thanks !
The only downside is that still you get some deps warnings with that version of @Angular-devkit

[alan-agius4]

Is this still reproducible? If so, can we please get a reproduction?

[mohamedaboelmagd]

@shane-arthur

Me and @kapilpatel20 are able to solve this issue.

The reason behind this is @angular-devkit/build-angular@0.803.19

It was @angular-devkit/build-angular@0.803.5 when we created the Angular Universal project then someone did npm install and it got updated due to ^ symbol.

We reverted the version back to @angular-devkit/build-angular@0.803.5 and it started working properly.

I have issue which solved from 0.803.7
so I can't back to 0.803.5