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
When i modify and save my files, i see Angular-cli generating the chunks again - However its not reading the files content and is still giving errors. I have to exit and re-run ng serve before it stops giving errors.
Which i renamed to SignupInterface but the compiler is still giving error:
Module '"/app/signup/signup.model"' has no exported member 'SignupInterface'.
After exiting and re-running ng serve the problem gets fixed but its really annoying having to change properties/class/interface names and then re-running compiler
@hassanasad I was not able to replicate it on classes. But I can confirm it only happens in the case of interfaces so seems to be an issue with interfaces. On running ng serve it only picks the interfaces already defined. Making any consecutive change in the interface doesn't pick up the changes. Shows below error.
ERROR in /Users/sumitarora/workspace/open-source/temp/aa/src/app/app.component.ts (17,5): Type '{ email: string; p2: string; }' is not assignable to type 'Signup'.
Object literal may only specify known properties, and 'p2' does not exist in type 'Signup'.
@sumitarora that is weird - its same for me on classes and interfaces both. Perhaps might be because i have both in the same file which i am testing with?
I'm having the same issues. I previously had the issues in beta 30, but got around it by downgrading @ngtools/webpack to version 1.2.4
Changes to html files will be reflected in the browser after rebundling. Changes to .ts files seem to trigger a rebundle, however do not get reflected in the browser until a new ng serve is run
I'm having this issue with custom typings, even when it's not in separate files.
I was trying to add custom matchers to Jasmine, and it's failing. Here's a minimal reproducible example:
In a fresh install (cli@1.0.0, angular@4.0.0, typescript@~2.2.0), all I've changed is app.component.spec.ts:
Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.
Activity
filipesilva commentedon Mar 24, 2017
Heya, does this only happen on interfaces?
hassanasad commentedon Mar 24, 2017
@filipesilva it happens for classes aswell.
Renaming a class doesn't register unless i restart the CLI.
ctrl-brk commentedon Mar 24, 2017
Same happens to me with ng test (4.0.0-rc.5)
sumitarora commentedon Mar 24, 2017
@hassanasad I was not able to replicate it on classes. But I can confirm it only happens in the case of interfaces so seems to be an issue with interfaces. On running
ng serveit only picks the interfaces already defined. Making any consecutive change in the interface doesn't pick up the changes. Shows below error.Changing
passwordtop2in the interface.hassanasad commentedon Mar 24, 2017
@sumitarora that is weird - its same for me on classes and interfaces both. Perhaps might be because i have both in the same file which i am testing with?
hassanasad commentedon Mar 24, 2017
@filipesilva, @sumitarora Ah - it happens for classes as well IF the file contains an interface.
For instance:
blakejolley commentedon Mar 24, 2017
I'm having the same issues. I previously had the issues in beta 30, but got around it by downgrading @ngtools/webpack to version 1.2.4
Changes to html files will be reflected in the browser after rebundling. Changes to .ts files seem to trigger a rebundle, however do not get reflected in the browser until a new
ng serveis run@angular/cli: 1.0.0
node: 7.7.4
npm: 4.3.0
os: windows 10
"@angular/common": "4.0.0",
"@angular/compiler": "4.0.0",
"@angular/core": "4.0.0",
"@angular/forms": "4.0.0",
"@angular/http": "4.0.0",
"@angular/platform-browser": "4.0.0",
"@angular/platform-browser-dynamic": "4.0.0",
"@angular/router": "4.0.0",
"@angular/cli": "1.0.0",
"@angular/compiler-cli": "4.0.0",
paullessing commentedon Mar 30, 2017
I'm having this issue with custom typings, even when it's not in separate files.
I was trying to add custom matchers to Jasmine, and it's failing. Here's a minimal reproducible example:
In a fresh install (cli@1.0.0, angular@4.0.0, typescript@~2.2.0), all I've changed is
app.component.spec.ts:This will pass on the first run, and on all subsequent runs throws error:
If anyone has a workaround other than
--single-run, I'd be very grateful for input.nerdmax commentedon Sep 14, 2017
+1
nerdmax commentedon Sep 14, 2017
Same issues. "@angular/cli": "1.4.1"
damienwebdev commentedon Sep 21, 2017
Still seeing this in "@angular/cli": "1.4.2"
WaleedMKasem commentedon Oct 10, 2017
still in "@angular/cli": "1.4.5",
uloga commentedon Nov 5, 2017
+1 I have the same issue with class based typing's and the class doesn't contain any interfaces.
uloga commentedon Nov 5, 2017
Ok, I've changed all the classes to interfaces, seems to be working now. Still using older version of cli @angular/cli: 1.2.6
alan-agius4 commentedon Dec 10, 2018
Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.
angular-automatic-lock-bot commentedon Sep 9, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.