tsconfig.json with extends not handled correctly

[eelco]

When passing a tsconfig.json to --ts-config madge does not handle the extends 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

config.tsConfig = obj.raw;

This is not correct. Compare to how filing-cabinet fixed the same issue: dependents/node-filing-cabinet#86 That code ends up using options for the processed compilerOptions, which is the result of merging in the options as configured via the file referred to with extends.

Found during debugging for this related issue: #322

[pedrolamas]

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

[vikingair]

@kamiazya will this be possibly fixed in V6?

[kamiazya]

@fdc-viktor-luft
I will work on it, but it may take some time to debug.

I think the response is that it is not required in the v6 release, but will be included if it is ready in time.