Skip to content

feat(@angular/cli): Add hmr support for ng new #5396

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

Closed
wants to merge 2 commits into from

Conversation

rob-balfre
Copy link

‘ng new -hmr’ will generate a project with hmr support

‘ng new -hmr’ will generate a project with hmr support
@hansl
Copy link
Contributor

hansl commented Mar 13, 2017

Please submit a design for every new features, and explain why you think this is important. We are also in a freeze right now and new features won't be added until 1.1.

I'd rather personally see an hmr flag default in the config than having to use it when creating a new app, but we're always open to discussion. File a feature request/proposal, and if there's interest we'll go forward with the design.

Also, that warning is there to make sure people understand what HMR means and how it limits their apps. Many application will not work with HMR, which was why we only did a flag in the first place.

@hansl hansl closed this Mar 13, 2017
@rob-balfre
Copy link
Author

@hansl thanks, will do. First attempt fail :)

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants