Angular-cli: Upgrade to 9 breaks ng-universal application.

[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/[email protected]
  └── [email protected]

[kaushikparmar]

@shane-arthur

Me and @kapilpatel20 are able to solve this issue.

The reason behind this is @angular-devkit/[email protected]

It was @angular-devkit/[email protected] 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/[email protected] 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/[email protected]

It was @angular-devkit/[email protected] 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/[email protected] and it started working properly.

Great!!! thanks bro!

[eternalmatt]

Replying "me too" except I am on [email protected] 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/[email protected]

It was @angular-devkit/[email protected] 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/[email protected] 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/[email protected]

It was @angular-devkit/[email protected] 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/[email protected] and it started working properly.

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

[at-dongho]

I change to "@angular-devkit/build-angular": "~0.800.0", and it work for me.

[alan-agius4]

Hi all, is this still reproducible using Angular CLI latest version 9 or prerelease of 10?

[alan-agius4]

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.

If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.

[angular-automatic-lock-bot[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._}