-
Notifications
You must be signed in to change notification settings - Fork 115
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
'component' is not a known element #14
Comments
Can you produce a repository that duplicates this? |
I'm not able to reproduce it in a new project, I'll come back to you if I succeed to reproduce it. |
This may be related to #36? |
@petebacondarwin Could be but without a solid repo it is hard to be sure. |
Please reopen if you can still reproduce this in |
version 0.1.2 |
@ialex90 Can you open a separate issue and attach either a .zip file that reproduces this or a github project I can clone? |
@chuckjaz I've tried this plugin in 2 different environments with the same result. I think if you import a module and try to use the component, will see the error. Haven't this happened to you in the latest version? It's a very common scenario and I've faced on Windows & MacOS. Do you need me to recreate this scenario? |
This is not the same issue as above which is why I would like a new issue open. Second, I always want to be very clear about what issue is being resolved. Having a repro attached to the bug helps with that immensely event if you believe the repro is trivial, please attach one. Also, note that structural changes (such as importing and modifying a module) take a few seconds to propagate because we are deferring some expensive calculations. Try modifying the source reporting the error a 5 to 10 seconds after you made the |
I have been creating a small project with a single ngmodule exported and imported and it works well with the plugin. I got the update today too, not sure if it's because of that, anyway, in the big project I'm working on, even with the newest version, it does trigger that error that I showed above and I can't replicate a scenario with 30-40 module just to see if triggers the error or not. I will wait if someone else has the same error or maybe in a near future I won't see those errors and will be able to use the plugin. |
I'm seeing this issue in v0.1.3. Everything works for me (compiles/runs etc), but my shared module components are still getting "not known element" errors. I've commented on #36 |
Having this issue in 0.1.9. Only seems to be affecting library components referenced from outside of the app's project structure, even when both project folders are loaded into vs code. e.g. referencing from "projects/shared-lib/src/public_api" shows no error, referencing from "../ngls-issue-lib/projects/ext-lib/src/public_api" can't resolve the component and shows an error. The app builds and runs without problems, displays all components. Reproduced in sample project at public repo: |
I'm also having a same issue |
i'm also having this issue while using a third party module |
Check to see if the component was imported and added to @NgModule declarations in your app.module.ts file. You may have to manually do the following: |
I'm still having this issue |
Add
on component module |
Having that on mac Catalaina 10.15.2 with angular material components that I am exporting from the custom angular material module that lives in my shared library in my monorepo VScode details:
By adding UPDATE: |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
When a custom component is imported via a module, it cannot be found inside a template, it shows:
The text was updated successfully, but these errors were encountered: