fb58a2bd54
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
1.2 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.