Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

angular cli hmr not reload component #62

Open
elvisbegovic opened this issue Jul 26, 2017 · 7 comments
Open

angular cli hmr not reload component #62

elvisbegovic opened this issue Jul 26, 2017 · 7 comments

Comments

@elvisbegovic
Copy link

elvisbegovic commented Jul 26, 2017

I use angular cli v 1.3rc0 and follow "stories hmr" from their wiki, it works well for a lot of component but there are some components that after file change, cli rebuild correctly and page is refresh (without reload whole browser like when press F5) this behavior is works perfectly BUT new edition aren't applied, always old one is there and when I pres F5 the edited text appear correctly.

Any idea?

@moshejs
Copy link

moshejs commented Aug 9, 2017

I'm having the same issue. Sometimes I need to refresh or recompile the build in order to see changes in the view.

@PatrickJS
Copy link
Owner

can you reproduce the issue in a repo so I can see what's going on

@elvisbegovic
Copy link
Author

Please apologize Difficult to me i have relativly big project. 70module 60lazyload module. Mabye you @moshejs can give us better input, example ?!?

Thanks to investigate

Cc @gdi2290

@moshejs
Copy link

moshejs commented Aug 10, 2017

I always update to the latest build (as of now: ng 4.3.3 / cli 1.3.0).

I don't know how to reproduce the issue, but here's the behavior:

dev changes HTML
HMR does it's thing...
view appears to "flicker" (state is reset transferred.)
...HMR update complete.
DOM doesn't update.

dev presses F5
The changes between updates can now be seen.

I think this is what OP is trying to say, I am having the same issue.

@cjntaylor
Copy link

cjntaylor commented Aug 16, 2017

I believe I've traced this issue. angular/cli > ~1.3.0 uses webpack ~3.4.1. I think the issue is that the generated modules are slightly different, so the code that attempts to reload the template doesn't work.

Downgrading to angular/[email protected] and ensuring that webpack ALSO downgrades to 2.x seems to revert this issue.

@moshejs
Copy link

moshejs commented Aug 16, 2017

And that will explain my first breaking change. Thank you for your work.

It would also help to, upgrade our code..

@svvac
Copy link

svvac commented Oct 27, 2017

Also see #70

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants