-
Notifications
You must be signed in to change notification settings - Fork 12k
Add new script 'ng update' #7375
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
Comments
That would be great, but any of these things could have been manually changed. What if the author wants those changes preserved? Then any time angular-cli is upgraded their changes would be overwritten. Currently when I upgrade angular-cli, I generate an entirely new project structure and then compare every file I can find against my own files, including:
It's some manual work but I'm not sure how this could be automatically done. |
There are many issues created from developers that do not update their apps properly, probably because they think that just changing the version in package.json is enough. There is #7334 and many more issues because of this. |
This is something that we talk about every now and then... It's true that a lot of issues are due to bad upgrades. Configuration items like the ones listed by @BurningDog could be upgraded automatically. A health check would also be nice, like verifying incompatible options or packages aren't set. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Feature Request
Description
When update the version of angular/cli, use ng update to update the configuration files like tsling.json and tsconfig.json etc. or and postinstall hooks to auto update the configuration files.
The text was updated successfully, but these errors were encountered: