support module references in extends (checking default tsconfig.json filename) #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed using
vitest
withunplugin-swc
that loadingtypescript
configuration fails when referencing a module without filename.Typescript itself and
esbuild
allow extending a tsconfig that is references as a module or path, without a filename.E.g. when a
tsconfig.json
file is exported in a node_module calledmy-tsconfig-module
(for example in a monorepo where a tsconfig module is a workspace that's symlinked to other packages as a module dependency)Then your tsconfig can reference it as:
And
typescript
will search for a/my-tsconfig-module
dir innode_modules
and look for atsconfig.json
file in it by default.This PR adds a try / catch to handle this case.