iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/aio/content/errors/NG8001.md

22 lines
1.1 KiB
Markdown
Raw Normal View History

docs: add guides for the top 10 errors (#40060) add top 10 error guides provide description and debugging for top errors PR Close #40060
2021-01-13 20:34:57 -05:00
@name Invalid Element
@category compiler
@shortDescription Unknown HTML element or component
@description
One or more elements cannot be resolved during compilation because the element is not defined by the HTML spec, or there is no component or directive with such element selector.
docs: add embedded videos to error guides (#40453) add embedded youtube videos provide visual debugging for top errors PR Close #40453
2021-01-20 00:17:25 -05:00
<div class="alert is-helpful">
This is the compiler equivalent of a common runtime error `NG0304: '${tagName}' is not a known element: …`.
</div>
docs: add guides for the top 10 errors (#40060) add top 10 error guides provide description and debugging for top errors PR Close #40060
2021-01-13 20:34:57 -05:00
@debugging
fix(docs-infra): use relative URLs for internal links on error pages (#40881) Previously, some of the links on the error pages had URLs prefixed with `https://angular.io/`. This caused them to be treated as external URLs, which had the following downsides: - Links would always point to `angular.io` instead of the same version as the error page (e.g. `next.angular.io` or `v11.angular.io`). - Dgeni would not be able to check that the URLs are valid (i.e. point to existing pages). - An external link icon would incorrectly be shown next to the links on `angular.io`. This commit fixes the links to use relative URLs. PR Close #40881
2021-02-18 11:42:45 -05:00
Use the element name in the error to find the file(s) where the element is being used.
docs: add guides for the top 10 errors (#40060) add top 10 error guides provide description and debugging for top errors PR Close #40060
2021-01-13 20:34:57 -05:00
fix(docs-infra): use relative URLs for internal links on error pages (#40881) Previously, some of the links on the error pages had URLs prefixed with `https://angular.io/`. This caused them to be treated as external URLs, which had the following downsides: - Links would always point to `angular.io` instead of the same version as the error page (e.g. `next.angular.io` or `v11.angular.io`). - Dgeni would not be able to check that the URLs are valid (i.e. point to existing pages). - An external link icon would incorrectly be shown next to the links on `angular.io`. This commit fixes the links to use relative URLs. PR Close #40881
2021-02-18 11:42:45 -05:00
Check that the name and selector are correct. If the component is from a different module or import, check that the component is exported from its origin module and imported into the correct `*.modules.ts` file, and declared in the imports list.
docs: add guides for the top 10 errors (#40060) add top 10 error guides provide description and debugging for top errors PR Close #40060
2021-01-13 20:34:57 -05:00
fix(docs-infra): use relative URLs for internal links on error pages (#40881) Previously, some of the links on the error pages had URLs prefixed with `https://angular.io/`. This caused them to be treated as external URLs, which had the following downsides: - Links would always point to `angular.io` instead of the same version as the error page (e.g. `next.angular.io` or `v11.angular.io`). - Dgeni would not be able to check that the URLs are valid (i.e. point to existing pages). - An external link icon would incorrectly be shown next to the links on `angular.io`. This commit fixes the links to use relative URLs. PR Close #40881
2021-02-18 11:42:45 -05:00
When using custom elements or web components, ensure that you add [`CUSTOM_ELEMENTS_SCHEMA`](api/core/CUSTOM_ELEMENTS_SCHEMA) to the app module.
docs: add guides for the top 10 errors (#40060) add top 10 error guides provide description and debugging for top errors PR Close #40060
2021-01-13 20:34:57 -05:00
If this does not resolve the error, check the imported libraries for any recent changes to the exports and properties you are using, and restart your server.