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.0 KiB
@name Missing Reference Target @category compiler @videoUrl https://www.youtube.com/embed/fUSAg4kp2WQ @shortDescription No directive found with export
@description
Angular can’t find a directive with {{ PLACEHOLDER }} export name. This is common with a missing import or a missing exportAs on a directive.
This is the compiler equivalent of a common runtime error NG0301: Export Not Found.
@debugging Use the string name of the export not found to trace the templates or modules using this export.
Ensure that all dependencies are properly imported and declared in our Modules. For example, if the export not found is ngForm, we will need to import FormsModule and declare it in our list of imports in *.module.ts to resolve the missing export error.
import { FormsModule } from '@angular/forms';
@NgModule({
...
imports: [
FormsModule,
…
If you recently added an import, you will need to restart your server to see these changes.