Add support for TS 5.5 ${configDir} template variable

[zanminkian]

Feature request

TS 5.5 support ${configDir} template variable. See here.

import { parseTsconfig } from "get-tsconfig";
const tsconfig = parseTsconfig('/path/to/tsconfig.json');
console.log(tsconfig.compileOptions.outDir) // if there is `${configDir}` template variable in `outDir`, the output result is incorrect in TS 5.5

Motivations

To support TS 5.5 ${configDir} template variable.

Alternatives

No response

Additional context

No response

Bugs are expected to be fixed by those affected by it

• I'm interested in working on this issue

Compensating engineering work financially will speed up resolution

• I'm willing to offer financial support

[SukkaW]

@privatenumber I'd like to create a PR for ${configDir} support, but I can't get existing test cases to pass after upgrading to TS 5.5 (it seems that there is a behavior change with --showConfig). You might wanna take a look at that first.

[privatenumber]

Yeah the tests need to be updated when you upgrade typescript. I'm not sure when I'll get around to this right now.

[SukkaW]

Yeah the tests need to be updated when you upgrade typescript. I'm not sure when I'll get around to this right now.

It seems that the latest tsc --showConfig now prints explicit config instead of the original config, hence the extra fields.

[privatenumber]

Yep, it's a good thing. get-tsconfig should match this behavior and build-in this logic.

[SukkaW]

Yep, it's a good thing. get-tsconfig should match this behavior and build-in this logic.

Though tsc --showConfig now makes the "hidden" default more explicit, I am not sure whether the get-tsconfig should do the same, this looks like a breaking change to me.

[privatenumber]

Before, it was up to the consumer of get-tsconfig's output to determine what configs are implicitly enabled, but now get-tsconfig does it for you. In terms of behavior, there's no breaking change, but there is a breaking change in terms of API output. I don't mind doing a major release for this.

[privatenumber]

@SukkaW
RE: dominikg/tsconfck#183

I'm quite occupied with work these days but if it's a priority, I'm happy to support you to get this in.

For now, we can upgrade TypeScript and suppress the extra output. Would you be willing to open a PR?

[SukkaW]

For now, we can upgrade TypeScript and suppress the extra output. Would you be willing to open a PR?

I already had a branch going. Lemme see what I can do.

Actually I suggest that we makes the tests passed first, that's to say, let's switch from toBeStrictEqual to loosely equal toMatchObject. And we can work on new behavior then.

[privatenumber]

Sounds good!

[privatenumber]

🎉 This issue has been resolved in version 4.8.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[SukkaW]

@privatenumber You might want to re-open this issue. #83 only fixes the test cases are doesn't actually implement the ${configDir} feature.

[privatenumber]

See eba8538

[SukkaW]

See eba8538

Oh I missed that!

[privatenumber]

This is a closed issue, please open another one.

Looks like I missed rootDirs and others (declarationDir, typeRoots, baseUrl). Feel free to open a PR