feat: use tsconfck instead of tsconfig-resolver

[Princesseuh]

Changes

tsconfig-resolver is unmaintained and doesn't support all of newer TypeScript's features. tsconfck is also in use by many reputable project and should be a safer dep to have.

Fix #6918

Testing

Tests should pass!

Docs

N/A

[changeset-bot]

🦋 Changeset detected

Latest commit: fad5457

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[natemoo-re]

LGTM. Thanks for pinning the exact pre-release version. We'll need to remember to keep an eye on that when it gets bumped to latest.

[github-actions]

This PR is blocked because it contains a minor changeset. A reviewer will merge this at the next release if approved.

[firxworx]

Looks good this is a nice contribution @Princesseuh :)
If the motivation is to support ts5 extends format / multiple extends do you think there should be a test / fixture that covers that case? Maybe I missed when I skimmed down files changed but I didn't catch. Thanks again!

[Princesseuh]

Looks good this is a nice contribution @Princesseuh :)
If the motivation is to support ts5 extends format / multiple extends do you think there should be a test / fixture that covers that case? Maybe I missed when I skimmed down files changed but I didn't catch. Thanks again!

We could for sure, but we'd rather avoid testing every feature like this that are ultimately outside of our code. We trust tsconfck to do what it says, especially considering it's used upstream from us (Vite uses it)