-
Notifications
You must be signed in to change notification settings - Fork 12k
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
ng update/add remove newline in package.json #11744
Comments
This issue also seems to occur in angular.json after |
This is very annoying, especially if you use sth like Prettier on CI, which requires newlines – to have consistent code formatting and green build you must add this newline after each update command. And to avoid diff cluttering |
…kage.json As stated in angular#11744, `ng update` command removed the newline at the end of the package.json file. This commit makes `ng update` to preserve newline, if it was present before running the command.
…kage.json As stated in angular#11744, `ng update` command removed the newline at the end of the package.json file. This commit makes `ng update` to preserve newline, if it was present before running the command.
…kage.json As stated in angular#11744, `ng update` command removed the newline at the end of the package.json file. This commit makes `ng update` to preserve newline, if it was present before running the command. Fixes angular#11744
…kage.json As stated in angular#11744, `ng update` command removed the newline at the end of the package.json file. This commit makes `ng update` to preserve newline, if it was present before running the command. Fixes angular#11744
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. |
Bug Report or Feature Request (mark with an
x
)Command (mark with an
x
)Versions
Repro steps
ng update @angular/something
Desired functionality
Not a big deal but
ng update
should add a newline at te end of package.json so that git doesn't complain anymore.The text was updated successfully, but these errors were encountered: