Registering a provider in app.module.shared does not work

[ukphillips]

I have an injectable service that I am attempting to register as a provider in my app.module.shared.ts, but at runtime I get the typical no provider for XXXservice error. When I move the provider registration to the app.module.client level everything seems to run fine.

[ADefWebserver]

I have found that Angular services (classes decorated with @Injectable()) now need to be registered in the app.module.client.ts file.

See:
Upgrading JavaScriptServices and PrimeNG From Angular 2 to Angular 4+

[MarkPieszak]

The shared file should actually be an NgModule itself that's imported into both client and server NgModules, that will fix that issue. As forRoot actually has to be called on a root NgModule.

[ADefWebserver]

The shared file should actually be an NgModule itself that's imported into both client and server NgModules, that will fix that issue.

Thanks @MarkPieszak, I updated my article with your directions. However, I think a lot of people will be lazy and just stick it in the client file.

[MarkPieszak]

The problem is the server will error if you only include something in Client and not both platforms.

[ADefWebserver]

The problem is the server will error if you only include something in Client and not both platforms.

I never use server rendering (I use PrimeNG and as of now it doesn't support that -- I think because of components it uses). Perhaps that is why I never had problems?

[SteveSandersonMS]

Thanks for letting us know. We'll need to clear this pattern up as part of fixing #986, so I'll close this issue as a duplicate of that one.