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

ng update comand not working #4765

Closed
fkolar opened this issue Feb 17, 2017 · 9 comments
Closed

ng update comand not working #4765

fkolar opened this issue Feb 17, 2017 · 9 comments

Comments

@fkolar
Copy link

fkolar commented Feb 17, 2017

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
MAC

Versions.

@angular/cli: 1.0.0-beta.31
node: 6.9.0
os: darwin x64
@angular/common: 2.4.7
@angular/compiler: 2.4.7
@angular/core: 2.4.7
@angular/forms: 2.4.7
@angular/http: 2.4.7
@angular/platform-browser: 2.4.7
@angular/platform-browser-dynamic: 2.4.7
@angular/router: 3.4.7
@angular/cli: 1.0.0-beta.31
@angular/compiler-cli: 2.4.7

I just updated form #30 to # 31 and after standard procedure of uninstalling and installing new NPMs I run ng update that usually works but now after first questions and aswer NO to skip it exits back to terminal


installing ng2
? Overwrite .editorconfig? (yndH) 

Is there any update task available for this version or should I create new empty project and update files manually?

Thank you,
frank

@prathamesh7pute
Copy link

Noticed same issue on windows also....
For now I am currently creating a new project and manually overwrite the files.

Also it will be good when we overwrite the files like package.json it will update the dependencies version only related to cli and not remove the independently installed dependencies like bootstrap

@fkolar
Copy link
Author

fkolar commented Feb 17, 2017

I see. so it must be something in new version. I just created new project and used merge tool and did little manual work.

@grizzm0
Copy link
Contributor

grizzm0 commented Feb 17, 2017

Dupe of #4653.
ng update was broken in beta 31 and has been removed from beta 32 in #4628

See changelog for more info: https://github.com/angular/angular-cli/blob/3ad2856b27889a50a742c9dca9554a190c8509bf/CHANGELOG.md

@fkolar
Copy link
Author

fkolar commented Feb 17, 2017

Cool. I will start again. I just hope in the next few minutes there will not be version 33 ;-)

@fkolar fkolar closed this as completed Feb 17, 2017
@grizzm0
Copy link
Contributor

grizzm0 commented Feb 17, 2017

Next release will be rc0.

@fkolar
Copy link
Author

fkolar commented Feb 17, 2017

You might want to also update documentation as in README.md there is still 👍

rm -rf node_modules dist # use rmdir on Windows
npm install --save-dev @angular/cli@latest
npm install
ng update

@itsnotvalid
Copy link

So the update doesn't work, what can we do to update? We now need to resolve to what @prathamesh7pute does before there was such command...

@grizzm0
Copy link
Contributor

grizzm0 commented Feb 17, 2017

To update you need to follow the breaking changes instructions in CHANGELOG.md

As of rc0 (next release) there will not be any more breaking changes.

@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 6, 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

No branches or pull requests

4 participants