-
Notifications
You must be signed in to change notification settings - Fork 12k
Project version in .angular-cli.json #4784
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
Meligy
added a commit
to Meligy/angular-cli
that referenced
this issue
Feb 17, 2017
Adds a note about updating the version number in `.angular-cli.json` Fixes angular#4784
shit, accidentally clicked |
#4795 💃 |
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is there any need of having project version property in
.angular-cli.json
?Sometimes it might be misleading (especially for ones who are not familiar with angular-cli yet) if you're not manually keeping it in sync with real one used in
package.json
.After
update/init
command deprecation it's so easy to miss to update it... 😞The text was updated successfully, but these errors were encountered: