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 does not run properly #4723

Closed
JoA-MoS opened this issue Feb 15, 2017 · 6 comments
Closed

ng update does not run properly #4723

JoA-MoS opened this issue Feb 15, 2017 · 6 comments

Comments

@JoA-MoS
Copy link

JoA-MoS commented Feb 15, 2017

Please provide us with the following information:

OS?

Windows 10

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

 / _` || '_ \  / _` || | | || | / _` || '__|_____  / __|| || |
| (_| || | | || (_| || |_| || || (_| || |  |_____|| (__ | || |
 \__,_||_| |_| \__, | \__,_||_| \__,_||_|          \___||_||_|
               |___/
@angular/cli: 1.0.0-beta.31
node: 6.9.2
os: win32 x64
@angular/common: 2.3.1
@angular/compiler: 2.3.1
@angular/compiler-cli: 2.3.1
@angular/core: 2.3.1
@angular/forms: 2.3.1
@angular/http: 2.3.1
@angular/platform-browser: 2.3.1
@angular/platform-browser-dynamic: 2.3.1
@angular/router: 3.3.1
@angular/cli: 1.0.0-beta.31

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.
updated from angular-cli beta.20-4 to beta.31
Followed the steps in the MD
got to the step where you run ng update and it asks if I want to update .editorconfig then I entered y pressed enter and it goes back to the command prompt

PS C:\dev\myapp> ng update
installing ng2
? Overwrite .editorconfig? Yes, overwrite
PS C:\dev\myapp>

I have tried every option Y, n, d all with the same result
I have tried in the standard windows command prompt both standard and as administrator
I tried in powershell both standard and as administrator
I even tried using bash on windows

All had the same result

The log given by the failure.

Normally this include a stack trace and some more information.

Mention any other details that might be useful.


Thanks! We'll be in touch soon.

@Da13Harris
Copy link

We experienced the same issue. As a workaround, since our files were already in source control (TFS), we deleted any that caused the "Overwrite" error and used TFS to manage our differences. Pretty painful, but it worked. (Well, aside from our new missing Webpack library error. :-/)

@JoA-MoS
Copy link
Author

JoA-MoS commented Feb 15, 2017

Thanks @Da13Harris, sounds a bit painful. Do you know if the ng update command works on a Mac or on other systems?

@1thrasher
Copy link

@SkiGeek82 It does not work on OSX either. I just followed @Da13Harris advice, and yes, it is painful.

@Meligy
Copy link
Contributor

Meligy commented Feb 15, 2017

Duplicate of #4653 / #4584.

@hansl
Copy link
Contributor

hansl commented Feb 16, 2017

Closing this as dupe of the 2 issues @Meligy pointed out.

@hansl hansl closed this as completed Feb 16, 2017
@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

5 participants