sagargurtu

Yes, that's what the issue is here. When `"module": "NodeNext"` and `"moduleResolution": "NodeNext"` are set, VSCode starts throwing above errors (might be because it starts treating the target as commonjs?...

This is resolved as of `[email protected]` and VS Code version 1.74.3. Closing this issue.

Hmm looks like the issue got resolved only for certain third-party packages (the ones I had in my project).