Remove usage of baseUrl from nx apps tsconfig.base.json

[mattlewis92]

We have been experimenting with the typescript-go port on our repo, and one of the issues we ran into was caused by nx setting the baseUrl property in the tsconfig.base.json to "." and issues surfacing due to people's IDEs inserting absolute imports like import foo from 'libs/my-lib/src/lib/some-file' instead of using the path mapping.

It looks like the intent is for typescript to drop the baseUrl option in the go port: microsoft/typescript-go#1299

As according to the docs, baseUrl was only designed for the AMD module system and is not recommended:

This feature was designed for use in conjunction with AMD module loaders in the browser, and is not recommended in any other context. As of TypeScript 4.1, baseUrl is no longer required to be set when using paths.

It would be great if nx could provide a migration that:

1. Removes the baseUrl from the root tsconfig.base.json
2. Updates all paths in the tsconfig.base.json to be prefixed with ./
3. As a stretch goal - updates any absolute imports to use path mappings instead

Then all nx library generators are updated when adding new path mappings to add the ./ prefix e.g.

Before:

"@org/my-lib": ["libs/my-lib/src/index.ts"],

After:

"@org/my-lib": ["./libs/my-lib/src/index.ts"],

[drewbitt]

Does this work in typescript-go with just a baseUrl change?

I did not get it to work recently if it had path aliases, as stated in, microsoft/typescript-go#516 (comment) and thought we would need to move to workspaces which nx does not offer a migration for, stating in https://nx.dev/technologies/typescript/recipes/switch-to-workspaces-project-references "We are investigating automating parts of this process with generators"

[mattlewis92]

Does this work in typescript-go with just a baseUrl change?

I did not get it to work recently if it had path aliases, as stated in, microsoft/typescript-go#516 (comment) and thought we would need to move to workspaces which nx does not offer a migration for, stating in nx.dev/technologies/typescript/recipes/switch-to-workspaces-project-references "We are investigating automating parts of this process with generators"

We are just running tsgo via nx run commands and the tsgo cli command, and it works pretty well for us. The only problem we really ran into was a handful of imports that were incorrectly using absolute imports, that worked with tsc because baseUrl was set to ..