Skip to content

Updating to new version ignores app root #3212

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

Closed
ialexivy opened this issue Nov 21, 2016 · 3 comments
Closed

Updating to new version ignores app root #3212

ialexivy opened this issue Nov 21, 2016 · 3 comments
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent type: bug/fix

Comments

@ialexivy
Copy link

Please provide us with the following information:

OS?

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

Versions.

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

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.
Changed angular-cli.json root folder, prefix,StyleExt

The log given by the failure.

Normally this include a stack trace and some more information.

Mention any other details that might be useful.

When updating to new version of angular-cli, it ignores custom root and prefix defined in angular-CLI.json


Thanks! We'll be in touch soon.

@filipesilva filipesilva added command: new P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent type: bug/fix labels Dec 22, 2016
@filipesilva
Copy link
Contributor

This is a bug, but I should mention that the solution will likely be to remove ng init and actually make an ng upgrade that (for now) would mostly just look at updating angular-cli.json and package.json.

We shouldn't need user-code changes for upgrades anymore.

@filipesilva
Copy link
Contributor

Closing as obsolete.

@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 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent type: bug/fix
Projects
None yet
Development

No branches or pull requests

3 participants