You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I then edit configs/tsconfig_editor.json and add an entry for test1.ts into the files list.
Expected behavior:
tsc notices that the extended config has changed and recompiles, also compiling test1.ts.
Actual behavior:
tsc does nothing.
My actual issue lies with vscode's language services integration (that doesn't update the language service results when the underlying extended config is changed by our build system), but it seems that this codepath (based on skimming the tsserver source) is broken here too. Looking at the tsserver logs, it seems a watch is setup for main/tsconfig.json but not for the file it extends from.
The text was updated successfully, but these errors were encountered:
TypeScript Version: Version 4.1.0-dev.20200914
Search Terms:
Watch mode, tsserver watch, watch
Code
/// main/tsconfig.json
/// configs/tsconfig_editor.json
/// main/test.ts
/// main/test1.ts
I ran tsc from the
main
directory like so:test
is compiled just fine.I then edit
configs/tsconfig_editor.json
and add an entry fortest1.ts
into the files list.Expected behavior:
tsc notices that the extended config has changed and recompiles, also compiling test1.ts.
Actual behavior:
tsc does nothing.
My actual issue lies with vscode's language services integration (that doesn't update the language service results when the underlying extended config is changed by our build system), but it seems that this codepath (based on skimming the tsserver source) is broken here too. Looking at the tsserver logs, it seems a watch is setup for
main/tsconfig.json
but not for the file it extends from.The text was updated successfully, but these errors were encountered: