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

Why do I need this as developer? This question and the terminology - 'hot module replacement' should be explained better. #45

Open
devin6391 opened this issue Jan 27, 2017 · 3 comments

Comments

@devin6391
Copy link

New developers and developers who might not need this feature in present, maybe due to less compilation time required in their normal development procedure, might not understand the idea of hot module replacement. Please explain this idea first and then tell us how to do it.

@klaaz0r
Copy link

klaaz0r commented Jan 30, 2017

The main advantage is in development time, Instead of having to reload the page it will automatically appear. Now this is not the most amazing thing. Keeping state is what really speeds up your development process. In a simple app this might seems like overhead, but if you are working on a multipage application and you are working on something 5 components deep it can be a pain to code -> safe -> recreate all the steps -> repeat

I hope this answers your question

@simeyla
Copy link

simeyla commented Jun 26, 2017

Please add something like this to the main page!

You will get a lot more people using your project if you explain it better. Also it would be very important to list the advantages and disadvantages. Keeping state sounds great but I think it is a very complicated thing and it would be good to know what does work or doesn't before I start.

@manikantag
Copy link

Angular's ng serve does the same, right? Is there any difference?

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

4 participants