Parse nested references

[Desteel]

Hi,

It seems that tsconfck only handles the first level of references, so with nesting like

//  tsconfig.json
{ "references": [{ "path": "./tsconfig.a.json" } ] }

//  tsconfig.a.json
{ "references": [{ "path": "./tsconfig.nested.json" } ] }

only the tsconfig.a.json will be available in the referenced property of the tsconfig.json, but tsconfig.nested.json won't be available in the referenced property of the tsconfig.a.json.

Is it intentional behavior and if so, is the only way to handle such cases to run the parsing manually for each nested config?

Thanks.

[dominikg]

does typescript itself work with nested references and do you have a usecase/example for this?

I'd rather avoid spending more work in parsing tsconfig files that don't apply to the input file

[Desteel]

Yes, I am not sure if it is a good idea or not to make such nested references (actually, I do not think it is a good idea), but this is a valid case. It can be found, e.g. in monorepos, where the first level is used as an entry point, and the second level is located inside monorepos projects.

I can research adding this feature sometime, e.g. with an option like 'shouldParseDeepReferenced', if you do not mind.

[dominikg]

unfortunately i do mind.

extra options need to be justified and make sense. So it would need to be demonstrated that typescript itself recognizes these nested references without a second pass, that people actually use it in the wild and that these users actually want to use tsconfck and can't live with a simple second pass calling tsconfck again themselves.