-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tsconfig.json
with extends
not handled correctly
#323
Comments
I've noticed this issue myself, only way so far I found of bypassing it is by creating a "merged" file and using that with madge: npx tsc --showConfig -p ./tsconfig.app.json > tsconfig.merged.json
npx madge@latest --ts-config ./tsconfig.merged.json --warning --circular --extensions ts,vue,js ./src |
@kamiazya will this be possibly fixed in V6? |
@fdc-viktor-luft I think the response is that it is not required in the v6 release, but will be included if it is ready in time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When passing a
tsconfig.json
to--ts-config
madge does not handle theextends
field correctly.It is calling all the “right” options to parse the file with TypeScript, but then ends up taking the
raw
field as the options:madge/bin/cli.js
Line 118 in 715f1a0
This is not correct. Compare to how
filing-cabinet
fixed the same issue: dependents/node-filing-cabinet#86 That code ends up usingoptions
for the processedcompilerOptions
, which is the result of merging in the options as configured via the file referred to withextends
.Found during debugging for this related issue: #322
The text was updated successfully, but these errors were encountered: