You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running ng serve to use the live reload in my development.
If I create a new component, say with BoardComponent with selector app-board, and add the app-board element to a parent's template before I declare BoardComponent in the Module, I get an error in the browser complaining that "app-board is not a known element". Even if we now remove the element from the parent's template, the error does not go away.
ng serve does not show any error, and restarting ng serve removes the browser error.
This does not occur if I declare BoardComponent in the Module before I add the element to the parent's template.
This is a problem because it disrupts the development workflow.
The log given by the failure.
From browser console:
Unhandled Promise rejection: Template parse errors:
'app-board' is not a known element:
If 'app-board' is an Angular component, then verify that it is part of this module.
If 'app-board' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the '@NgModule.schemas' of this component to suppress this message.
The text was updated successfully, but these errors were encountered:
OS?
Mac OSX Sierra (10.12.3)
Versions.
@angular/cli: 1.0.0-beta.30
node: 7.4.0
os: darwin x64
@angular/common: 2.4.6
@angular/compiler: 2.4.6
@angular/core: 2.4.6
@angular/forms: 2.4.6
@angular/http: 2.4.6
@angular/platform-browser: 2.4.6
@angular/platform-browser-dynamic: 2.4.6
@angular/router: 3.4.6
@angular/cli: 1.0.0-beta.30
@angular/compiler-cli: 2.4.6
Repro steps.
I'm running
ng serve
to use the live reload in my development.If I create a new component, say with
BoardComponent
with selectorapp-board
, and add theapp-board
element to a parent's template before I declareBoardComponent
in the Module, I get an error in the browser complaining that "app-board is not a known element". Even if we now remove the element from the parent's template, the error does not go away.ng serve
does not show any error, and restartingng serve
removes the browser error.BoardComponent
in the Module before I add the element to the parent's template.This is a problem because it disrupts the development workflow.
The log given by the failure.
From browser console:
The text was updated successfully, but these errors were encountered: