Is it expected that tsconfig resolves against the calling directory even when --cwd is specified? I have a use case where I have a browser lib and a node lib in the same repo that have distinct tsconfig.json files. Currently I have to specify the full path to make tsconfig.json discovery work, that is --cwd a/b/c --tsconfig a/b/c/tsconfig.json instead of just --cwd a/b/c --tsconfig tsconfig.json or just --cwd a/b/c. Is there some other configuration that I do not know about that would make this more intuitive?
Is it expected that
tsconfigresolves against the calling directory even when--cwdis specified? I have a use case where I have a browser lib and a node lib in the same repo that have distincttsconfig.jsonfiles. Currently I have to specify the full path to maketsconfig.jsondiscovery work, that is--cwd a/b/c --tsconfig a/b/c/tsconfig.jsoninstead of just--cwd a/b/c --tsconfig tsconfig.jsonor just--cwd a/b/c. Is there some other configuration that I do not know about that would make this more intuitive?