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've spent a while in the debugger on this, and the root cause appears to be how the export= SymbolObject is constructed in the source file's symbol.exports property in a JavaScript module source file versus a TypeScript module source file. This causes resolveESModuleSymbol to return undefined.
Being it applies only to this specific construct (i.e. assignments to exports. work with es6 imports, or importing with var <id> = require(...) syntax works), its not a total blocker. But would be good to fix ASAP, especially as the error is rather unattractive.
The text was updated successfully, but these errors were encountered:
See commented out failing test in this pull request.
I've spent a while in the debugger on this, and the root cause appears to be how the
export=
SymbolObject is constructed in the source file'ssymbol.exports
property in a JavaScript module source file versus a TypeScript module source file. This causesresolveESModuleSymbol
to returnundefined
.Being it applies only to this specific construct (i.e. assignments to
exports.
work with es6 imports, or importing withvar <id> = require(...)
syntax works), its not a total blocker. But would be good to fix ASAP, especially as the error is rather unattractive.The text was updated successfully, but these errors were encountered: