42289f25c6
The purpose of the changes is to clean all markdown to match a single pedantic style.
* To ensure all changes in style are properly separated.
* To ensure all styled content aligns to nearest 4-character-tab.
* To ensure all code blocks use the Angular `<code-example>` or `<code-tab>` elements.
* To ensure all markdown exists outside of html tags.
* To ensure all images use the Angular style for `<img>` elements.
* To ensure that all smart punctuation is replaced or removed.
```text
’, ’, “, ”, –, —, …
```
* To ensure all content does not conflict with the following reserved characters.
```text
@, $, *, &, #, |, <, >,
```
* To ensure all content displays using html entities.
The following changes were made to files in the following directory.
```text
aio/content
```
The target files were markdown files.
The list of excluded files:
```text
.browserslistrc, .css, .conf, .editorconfig, .gitignore, .html, .js, .json, .sh, .svg, .ts, .txt, .xlf,
```
PR Close #45325
1.3 KiB
@name Export Not Found @category runtime @videoUrl https://www.youtube.com/embed/fUSAg4kp2WQ @shortDescription Export not found!
@description
Angular can't find a directive with {{ PLACEHOLDER }} export name. The export name is specified in the exportAs property of the directive decorator. This is common when using FormsModule or Material modules in templates, and you've forgotten to import the corresponding modules.
This is the runtime equivalent of a common compiler error NG8003: No directive found with export.
@debugging Use the export name to trace the templates or modules using this export.
Ensure that all dependencies are properly imported and declared in your NgModules. For example, if the export not found is ngForm, we need to import FormsModule and declare it in the list of imports in *.module.ts to resolve the error.
import { FormsModule } from '@angular/forms';
@NgModule({ … imports: [ FormsModule, …
If you recently added an import, you may need to restart your server to see these changes.
@reviewed 2022-02-28