providedIn: ‘root’ is the easiest and most efficient way to provide services since Angular 6: The service will be available application wide as a singleton with no need to add it to a module’s providers array (like Angular <= 5). If the service is only used within a lazy loaded module it will be lazy … Read more
You can try this using loadChildren where the homeModule, productModule, aboutModule have their own route rules. const routes: Routes = [ { path: ‘home’, loadChildren: ‘app/areas/home/home.module#homeModule’ }, { path: ‘product’, loadChildren: ‘app/areas/product/product.module#ProductModule’ }, { path: ‘drawing’, loadChildren: ‘app/areas/about/about.module#AboutModule’ } ]; export const appRouting = RouterModule.forRoot(routes); and the home route rules will be like export const … Read more
As per the final version of Angular 2, services provided by a module are available to every other module that imports it. The Official Style Guide advice that application-wide services (singletons) that are to be reused anywhere in the application should be provided by some Core Module, that is to be imported in the main … Read more
Working with atom (1.21.1 ia32)… i got the same error, even though i added a reference to my pipe in the app.module.ts and in the declarations within app.module.ts solution was to restart my node instance… stopping the website and then doing ng serve again… going to localhost:4200 worked like a charm after this restart
According @CrazyMac’s comment, a good way would be to create a DirectivesModule. Inside this module you can declare and import all your directives then you will be able to import this module anywhere you want. app/modules/directives/directives.module.ts import { NgModule } from ‘@angular/core’; import { HighlightDirective } from ‘./highlight.directive’; @NgModule({ imports: [], declarations: [HighlightDirective], exports: [HighlightDirective] … Read more
Okay, after fiddling around with this for the better part of the weekend I got it running on my end. What worked for me in the end was to do the following: Export all Routes for every module you want to route. Do not import any of the RouterModule.forChild() in the child modules. Export every … Read more
Import BrowserModule, BrowserAnimationsModule, HttpModule or HttpClientModule only once, preferably in your root module.
This was a simple error. It occurred due to the missing {} around the module name in the import statement itself. Since this killed 2-3 hours of my time, sharing with you all so you won’t waste yours. Hope this can help someone. Cheers, Abhi.