-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'ngx-skeleton-loader' is not a known element: #3
Comments
Hi @tranvannhat . Could you share more information about the issue, please? Have you tried the Demo example? https://stackblitz.com/edit/ngx-skeleton-loader-sample?file=app%2Fapp.component.html |
Closing this issue due to the lack in reply. Thanks @tranvannhat , feel free to reopen it if needed |
you should add |
I got the same problem
// app.component.html And here is the error
P/S: package.json
|
@haucongle Looks like you're missing something in your local configuration. Could you check the stackblitz example (https://stackblitz.com/edit/ngx-skeleton-loader-sample?file=app%2Fapp.module.ts), please? The previous issue was solved by adding this step in the docs. If this issue still persists, could you please share a stackblitz link simulating your issue? |
@willmendesneto I think I know what my problem is now because I put tag |
Sure thing. What I can suggest for now is to add it in the correct module until we have a |
does it still not support for root ?? |
@LeentechDev Unfortunately, I didn't have proper time to look at it. I'll try to apply that in the next weeks. This can be a great opportunity for pull requests. Until we have the support in place, I strongly suggest you to use #3 (comment) as a solution. |
@willmendesneto I'm still getting the following error : 'ngx-skeleton-loader' is not a known element:
after importing NgxSkeletonLoaderModule from 'ngx-skeleton-loader' in my app.module.ts and also the parent module of the component. |
Hi @Sayrai. Could you share more information about the issue, please? If possible, could you fork and create an example based on the Stackblitz demo? At first, moment, looks like a issue with module configuration really, but it's good to get more details about it. So that I can help your scenario. https://stackblitz.com/edit/ngx-skeleton-loader-sample?file=app%2Fapp.component.html |
Also, I'm happy to share there's a new E.G. import { NgModule } from '@angular/core';
import { NgxSkeletonLoaderModule } from 'ngx-skeleton-loader';
// ... list of other app dependencies
import { AppComponent } from './app.component';
// ... list of other app components/modules
@NgModule({
declarations: [AppComponent],
imports: [NgxSkeletonLoaderModule.forRoot()],
providers: [],
bootstrap: [AppComponent],
})
export class AppModule {} |
In addition of that, I just updated the examples to use the new |
same issue :(
app.module.ts
"ngx-skeleton-loader": "^2.6.2", |
Any solution for this ? I'm facing the same issue, both importing
Thanks! |
This is an old issue related to a misconfiguration, as mentioned in this comment here #3 (comment) . In any case, I'm more than happy to help, but it would be great if I can have a real scenario simulation. Could you folks fork this Stackblitz example, simulate the issue, and share the link here, please? https://stackblitz.com/edit/ngx-skeleton-loader-user-card-component-sample |
Hi there, I use Angular 9.1.3. I try to follow the guild and import the Module like this. but it still show this error
|
Hi @johnMyjourney . The issue you're facing is related to some misconfiguration in your application. To solve that, please follow these steps and check the Stackblitz example as linked in this comment #3 (comment) In case you feel is not related to that, could you please provide a Stackblitz link that simulates your issue and share it, please? Cheers! |
This is still happening on Angular 15 with a fresh install of ngx-skeleton-loader. I could not find any compatibility list if ng version is the problem. |
I follow doc, but get error: 'ngx-skeleton-loader' is not a known element:....
The text was updated successfully, but these errors were encountered: