Fix esModuleInterop not being respected for JS CommonJS imports#2693
Draft
Fix esModuleInterop not being respected for JS CommonJS imports#2693
Conversation
For JavaScript CommonJS modules with `module.exports = { ... }`,
the binder creates an export= symbol with SymbolFlagsProperty, not
SymbolFlagsValueModule. This was causing TS2497 to be emitted even
when esModuleInterop was enabled.
The fix adds a check in resolveESModuleSymbol to skip the error for
JavaScript files when esModuleInterop is explicitly enabled.
Fixes #1124 and related issue #1054
Co-authored-by: jakebailey <5341706+jakebailey@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix tsgo not respecting esModuleInterop in certain cases
Fix esModuleInterop not being respected for JS CommonJS imports
Feb 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
tsgo reports TS2497 when importing named exports from CommonJS JavaScript files even when
esModuleInterop: trueis set. tsc allows these imports without error.Root Cause
The Go binder creates an
export=symbol withSymbolFlagsPropertyformodule.exports = { ... }, while TypeScript exports each shorthand property directly. The property symbol lacksSymbolFlagsModule | SymbolFlagsVariable, triggering the interop error check inresolveESModuleSymbol.Changes
ESModuleInterop.IsTrue()(uses tristate, not the deprecated always-trueGetESModuleInterop())Original prompt
esModuleInteropin certain cases #2692💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.