[ng update] Allow specifying path to tsconfig file

🚀 Feature request

Command (mark with an x)

- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [x] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Description

Considering there is a project with tsconfig.ts file somewhere deep in folder structure. Node_modules folder and package.json file lays in the root of an application. When running "ng update" command from the root of an application it will update package.json and throw an error saying "Could not find any tsconfig file. Cannot migrate DOCUMENT to new import source". Which is obvious, since there is no single tsconfig on the root, but multiple tcsonfig files across the application.

Describe the solution you’d like

It would be great if we could run migration tool specifying a path to tsconfig.ts file.

Describe alternatives you’ve considered

Updating all files manually is painful. The folder structure is designed this way for a reason and is unlikely to be changed.

[alxhub]

I think the root issue here is attempting to apply an ng update migration to a non-CLI application? I don’t believe we support this use case today. You might have some luck running the migration scripts manually, but I don’t know off the top of my head how to do this.

[angular-automatic-lock-bot[bot]]

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.}