baseUrl removal caused multiple libraries to fail

[hamidrezahanafi]

We are using typescript go in a nx monorepo and we couldn't update past 0711 version

I have two library failures

• nx is failing because it depends on baseUrl to set the swc baseUrl, I could workaround this by using two separate tsconfig files
• storybook is failing because it depends on TsconfigPathsPlugin and it has trouble importing correct path when baseUrl is missing and override doesn't work on this library and after a few hours of tinkering I could not find any workaround

Both of these libraries should fix their code to support omitting the baseUrl and I will follow up with them for a fix, but while doing that, is it possible to bring back the baseUrl support? I should note that this effect monorepo configuration since they depend on the baseUrl to resolve correct paths
I strongly believe it will impact the adoption of tsgo in short term.

[jakebailey]

baseUrl was never supported here, it just silently did nothing. Are you just asking to not have the error itself?

I would be shocked if swc didn't support a missing baseUrl.

tsconfig-paths definitely supports a missing baseUrl (which first became legal in TS 4.1; I filed that issue myself in 2020! jonaskello/tsconfig-paths#143), are you sure you're not just out of date?

[hamidrezahanafi]

baseUrl was never supported here, it just silently did nothing. Are you just asking to not have the error itself?

I would be shocked if swc didn't support a missing baseUrl.

tsconfig-paths definitely supports a missing baseUrl (which first became legal in TS 4.1; I filed that issue myself in 2020! jonaskello/tsconfig-paths#143), are you sure you're not just out of date?

Yes you are absolutely right, both swc and tsconfig-paths supports it but some of these big libraries like nx and storybook use them and forcing to use baseUrl especially on a monorepo context and they use that to resolve paths which might be very well incorrect usage of the option, since the baseUrl is not deprecated on typescript website.
Right now the storybook for example doesn't give me an option to override tsconfig-paths options (they say they do but it's not working and I think it's a bug) and nx is using tsconfig baseUrl to set swc base url and it stops at this line

My ask is to keep the option in (possibly adding a message for deprecation even though it's not being used) until we can fix upstream libraries if it doesn't cause any issues

[jakebailey]

The option is deprecated in TS 6.0, and this repo is for work on TS 7.0, so we have been operating on the assumption that all deprecations are hard errors and did not port any deprecation logic.

Right now the storybook for example doesn't give me an option to override tsconfig-paths options

Does this not come down to whatever version you depend on? I can see that they have tsconfig-paths@^4.0.0 which is new enough to not need baseUrl.

[hamidrezahanafi]

Yes it's not tsconfig-paths library itself but the way storybook is using it with their webpack plugin which is very dependant baseUrl and absoluteBaseUrl on the plugin, don't know what the exact fix is yet.

The option is deprecated in TS 6.0, and this repo is for work on TS 7.0, so we have been operating on the assumption that all deprecations are hard errors and did not port any deprecation logic.

I am wondering if we can delay deleting it so these libraries would catch up and make sure they support no baseUrl in more cases, if it's not the case, we can probably stay on 0711 version and push for fixes upstream

[hamidrezahanafi]

I just started filing issues with the libraries and pasting here for anyone else who might have the same problem

nx: nrwl/nx#32009

[controversial]

I am wondering if we can delay deleting it

Deleting it is delayed until Typescript 7.0—it’s planned to be deprecated in Typescript 6.0, which hasn’t even been released yet!

The tsgo codebase has never had baseUrl support; “delay deleting it” would mean the maintainers would have to develop the already-deprecated baseUrl functionality for the first time, knowing they’re about to go back and remove it later.

This seems like it would be a big waste of effort, to support a feature that will have already been deprecated for a whole major version by the time tsgo is released.

[hamidrezahanafi]

This seems like it would be a big waste of effort, to support a feature that will have already been deprecated for a whole major version by the time tsgo is released.

Definitely, I meant mostly to just keep the definition in for now (as it was before 0712 version) since other libraries are actively using it internally until they can fix upstream, also it will definitely allow more users to test preview version and give feedback here. But I understand that's not a desirable move.

Also filed a bug with Storybook
storybookjs/storybook#32107