I faced it last week again. My first above comment is still valid, I think it may happen sometimes if you are working and modidying components or components called in components, something like
while having ionic serve running
Modification in a page => Reload ok
Modification in a component used in a page => Reload probably always ok too
Modification in a component used in a componennt used in a page => Mmmmh not sure, not always
Something like that but couldn’t identify it 100%
Yep I think you captured the problematic path. Have the same issue.
I still have this problem to this day. The issue is for sure related to editing modules that are exported for use in other modules. Some deep pathing issues it seems.
Any fixes for this?? Super annoying, omg I have to build 2x for the html to change
Same here.
I’ve started using ionic since a week ago and this interrupts my flow every time cause I need to go in and re-save several .ts files to fix the issue. My latest issue (although I’ve experienced several throughout the week) was:
I created a new pipe, there was an initial syntax error with it (perhaps causing the error chain). I fixed the syntax error with the pipe, and suddenly I get an error message about a null function in one of my providers. I go in and simply resave that provider file with no modifications and that message disappears. But I get yet another error message about a missing function in yet another provider, I resave that one. And everything works.
Althought it is easy to fix, this bug is continuously breaking my working flow, I forget what I was actually trying to accomplish. Of course making the ionic (learning) experience very problematic.
Please take a good look at how ionic serve is caching files, because I suspect it is somehow using old files when things go south. Of course, it may also be my environment:
I’m on a Mac OS X using Chrome with “No Cache” addon. Using ionic 3.19.1. I’m using ionic serve -c command
Is it fixed already? I have ionic-apps 3.1.11 and issue still exists for me…
Still the same problem, it slows down the development a lot
I’m on "@ionic/app-scripts": "^3.2.0", and still have this problem.
I’m also 100% sure this has nothing to do with browser caching. I can see old data in the www folder.
This annoying problem popped it’s head up again on latest version of ionic.
Solved it by serving to a different port ionic serve -p 8101