VSCode does not show some typescript `isolatedModules` errors about typescript HOT 3 OPEN

Note: I'm not sure if this is a vscode or a typescript bug.
The issue specifically manifests within VSCode - hence I'm starting here.

I would assume that there is a breakage here due to the TS project service not properly respecting isolatedModules + project references?

from typescript.

It's worth noting that fixing this would likely cause some strife for people due to #37774

In the current state the IDE shows no errors and it's possible to work around/hide the "incorrect" CLI errors with a custom tsc wrapper.

If this bug is fixed then the IDE would show errors and there would be no way to silence them.

So they might best be solved together so that the IDE only shows these errors for "truly invalid" usecases (eg accessing a const enum from a node_module where the existence of preserveConstEnum can't be determined) and no errors are shown for "valid" usecases (eg accessing a const enum from a project reference)

from typescript.

I think that this bug is basically expected behavior that falls out of the poor design or bug that is #37774. I want to try to address #37774 directly to close this.

from typescript.