-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Remove extraneous top-level await requirement #37794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@Vandivier TLA await are invalid in script files. Deno loads every file as an ESM file, but to VSCode your example doesn't look like a module, so it it is treating it like a script. The current canonical way to for a file to be a module instead of a script when there are no other imports or exports is to include an There is a proposal for a pragma to force modules, but it is Stage 1 (early stages) in TC39. |
This issue has been marked as 'Question' and has seen no recent activity. It has been automatically closed for house-keeping purposes. If you're still waiting on a response, questions are usually better suited to stackoverflow. |
@kitsonk We now have a way to know whether files are implicitly to be treated as modules though, i.e. Not sure why target in |
Addressed at #36036 (comment) |
This may be a bug, I'm not sure. So I'm submitting as a feature request.
Search Terms
await
,top-level
,disable rule
Suggestion
"isolatedModules": true,
should not be required to remove top-level await error.Use Cases
I'm scripting a very simple file I/O script using Deno. The script runs without issue. Full code is in the below example.
Even though it works, VS Code complains. I think the complaint is at the TS level and I can't ignore it as a specific error. I can ts-ignore line-by-line, but that's not satisfactory.
The error is
'await' expressions are only allowed at the top level of a file when that file is a module, but this file has no imports or exports. Consider adding an empty 'export {}' to make this file a module.ts(1375)
Examples
Checklist
I have no idea whether this feature meets the items in the checklist.
Related Issues
await
error message is extremely unclear #36036The text was updated successfully, but these errors were encountered: