Ignore tsconfig provided by smithy-typescript, and extend root TSConfig while running generate-clients

[trivikr]

Is your feature request related to a problem? Please describe.
The PR #1297 creates root TSConfig for packages/*, but it doesn't apply to clients/* as the clients generated by smithy-typescript should be able to work independently. They need not be part of a monorepo setup.

Because of this, the internal dependencies are not navigable in clients as shown in the screenshot

Screenshot

Describe the solution you'd like

Let smithy-typescript emit tsconfig as it wants, but it should be overriden to extend root TSConfig by generate-clients command.

Describe alternatives you've considered
Sticking with individual TSConfig files for clients

[trivikr]

Closed by mistake.

smithy-typescript will emit a separate TSConfig, as clients should be able to work on their own in an independent repository. The ask is to use central TSConfig in aws-sdk-js-v3 monorepo.

[github-actions]

Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.