Closed DanielSidhion closed 1 year ago
@jonaskello pinging you because you seem to handle merging PRs in this repo. What's your review and release process like? This PR will help me migrate a bunch of projects I have to TypeScript 5.0 (as long as tsconfig-paths-webpack-plugin also works well with this change, but I'll take a look at that one once this PR is done).
I'm blocked by this as well (via eslint-plugin-import
). TS 5 started its beta 2 months ago :)
Patch coverage: 82.60
% and project coverage change: +0.27
:tada:
Comparison is base (
910a138
) 68.16% compared to head (540a1c1
) 68.43%.:exclamation: Current head 540a1c1 differs from pull request most recent head 62c1b80. Consider uploading reports for the commit 62c1b80 to get more accurate results
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
It'd be great if this could be backported to v3 as well, which has 3-4 times the downloads of v4.
Would be great to merge this one because it is blocking projects that uses esbuild to migrate to typescript 5
@DanielSidhion If I understand correctly this change is not breaking and could be released in a minor version?
@DanielSidhion If I understand correctly this change is not breaking and could be released in a minor version?
That's correct, I kept the same behaviour as before for any extends
that's just a string, and TS 5.0 doesn't introduce any breaking changes to how it handles extends
that are strings AFAIK.
Released in 4.2.0
@jonaskello any plans to backport this to v3?
Fixes #244.
TypeScript 5.0 added support for defining "extends" as an array of strings. This commit adds support for this use case.
It's important to note that even with this change, "baseUrl" and "paths" are still always being completely overwritten if a later tsconfig redefines any of those values. This might be confusing because a tsconfig may define "baseUrl=value1" and its own set of "paths" based on that baseUrl, but if a later tsconfig defines its own "baseUrl=value2", the overall config ends up becoming "baseUrl=value2" with the "paths" from the first config.
This behaviour hasn't changed even when "extends" is an array of strings, so this commit maintains this behaviour.