Make ngx-skeleton-loader standalone compliant

[alfmos]

I'm submitting a ... (check one with "x")

• bug report => search github for a similar issue or PR before submitting
• feature request

Current behavior
using ngx-skeleton-loader in a standalone app requires to import the module requires using ImportFromProviders

Expected behavior
import ngx-skeleton loader in standalone way, that is with a function like provideSkeletonLoader({config: configOptions})

What is the motivation / use case for changing the behavior?
As Angular evolves, modules are being stripped off, favoring direct import of components/services

Please tell us about your environment:

we use Angular 16, ubuntu 20, npm
web server is nginx and backend is in go

[caboodal]

Could somebody show how you use this component with standalone components, the above mentions ImportFromProviders, what is that and how is it implemented?

I've tried importFromProviders in my component route but I still cannot use the skeleton component in my component?

[caboodal]

Just in case anybody arrives here trying to use the component in standalone components...

Add the importProvidersFrom function call into your app.config.ts file as shown below.

export const appConfig: ApplicationConfig = {
	providers: [
		provideRouter(routes, withComponentInputBinding()),
		provideAnimations(),
		importProvidersFrom(
			NgxSkeletonLoaderModule.forRoot({ animation: 'pulse' }),
		),
	],
};

Then simply import the NgxSkeletonLoaderModule module into your component using the imports property. You can then use the <ngx-skeleton-loader> component in your standalone component.

[willmendesneto]

Thanks for sharing this @caboodal . There's a working in progress to integrate this feature. Until it didn't get finished, here's the approach to integrate in Angular Apps