feat: inherited import aliases in tsconfig #32
Merged
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.
This PR adds support for
paths
(andbaseUrl
) that are defined in a parenttsconfig.json
, linked using theextends
field. I came across this issue because this is the default setup for nx projects.The PR adds node.js style resolution of the
extends
field, and guards against infiniteextends
loops. I pulledresolveJson5File
out into a separate file as it seemsrequire.resolve
is pretty impossible to mock for the tests. The PR changes the logic to eagerly resolvebaseUrl
into an absolute path, as the value is always relative to whichever config file it was defined in.I tested using this nx template which uses a parent tsconfig to import the util styles: https://github.com/domharries/cssmodules-nx-example/blob/main/apps/cssmodules-nx-example/src/app/app.tsx