Getting HttpInterceptingHandler is not a constructor error while universal rendering

I’m trying to setup the server side rendering of my angular app, I have followed the instruction from here:

https://github.com/angular/angular-cli/wiki/stories-universal-rendering

Every command runs successfully, but after starting node server, when I try to visit the url, It throws the following error:

TypeError: _angular_common_http__WEBPACK_IMPORTED_MODULE_5__.ɵHttpInterceptingHandler is not a constructor
    at zoneWrappedInterceptingHandler (/Stuff/Development/Angular/angular-tuts/universal/dist/server.js:4040:23)
    at _callFactory (/Stuff/Development/Angular/angular-tuts/universal/dist/server.js:14256:20)
    at _createProviderInstance$1 (/Stuff/Development/Angular/angular-tuts/universal/dist/server.js:14210:26)
    at initNgModule (/Stuff/Development/Angular/angular-tuts/universal/dist/server.js:14143:32)
    at new NgModuleRef_ (/Stuff/Development/Angular/angular-tuts/universal/dist/server.js:14872:9)
    at Object.createNgModuleRef (/Stuff/Development/Angular/angular-tuts/universal/dist/server.js:14861:12)
    at NgModuleFactory_.create (/Stuff/Development/Angular/angular-tuts/universal/dist/server.js:17394:25)
    at /Stuff/Development/Angular/angular-tuts/universal/dist/server.js:9693:43
    at ZoneDelegate.invoke (/Stuff/Development/Angular/angular-tuts/universal/dist/server.js:515:26)
    at Object.onInvoke (/Stuff/Development/Angular/angular-tuts/universal/dist/server.js:9035:33)

Can anybody please help me with this?

Stackoverflow question reference: https://stackoverflow.com/questions/50781778/httpinterceptinghandler-is-not-a-constructor-while-universal-rendering-angularjs

[twoheaded]

Looks like it’s a conflict between platform-server@6.0.4 and angular/common@6.0.3. Was fixed in https://github.com/angular/angular/commit/60aa943e2dd4654600c0e53e51b8d7a1ac3730da.

Update your angular dependencies:

ng update @angular/core

It helped me

[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.}