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
The next minor release of TypeScript (4.7) should include a new moduleDetection option, which has to deal with how modules are detected by TypeScript when type checking. The default is "auto", which might be ok for us, but also there is "force" which is more the behaviour that we would expect for code running under Deno. We need to do a bit of experiment and testing.
The issue mostly manifested itself around issues in the lsp when having a file open with no top level import or export statement being treated a global script for type checking purposes. There were also some issues with emitting @jsxImportSource with modules that appeared to be scripts.
The text was updated successfully, but these errors were encountered:
kitsonk
added
feat
new feature (which has been agreed to/accepted)
tsc
related to the TypeScript tsc compiler
labels
Mar 12, 2022
Disregard previous comments. We should just use "moduleDetection": "force" all the way, I misunderstood that modules refer to both esm and cjs, as opposed to old-fashioned browser scripts.
Ref: microsoft/TypeScript#47495
The next minor release of TypeScript (4.7) should include a new
moduleDetection
option, which has to deal with how modules are detected by TypeScript when type checking. The default is"auto"
, which might be ok for us, but also there is"force"
which is more the behaviour that we would expect for code running under Deno. We need to do a bit of experiment and testing.The issue mostly manifested itself around issues in the lsp when having a file open with no top level import or export statement being treated a global script for type checking purposes. There were also some issues with emitting
@jsxImportSource
with modules that appeared to be scripts.The text was updated successfully, but these errors were encountered: