asume es module when using top level await

[jimmywarting]

I'm faced with this error:

'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)

when i have code such as await 1

it's not always that i import or export something
And i don't really feel like doing and empty export {} or adding any tsconfig.json or jsconfig.json
i have checkJS + allowJs turned on in my vscode settings and the environment it guesses that it's in is sometimes often wrong.

can you just don't assume that it's okey to use top level await.
I want to disable this lint/rule check completely completely... cuz this one is annoying.

[jcalz]

There’s a template you’re supposed to fill out when you open a new issue.

Looks like a duplicate of #37794.

[RyanCavanaugh]

You can set moduleDetection: force

[jimmywarting]

where in vscode? don't have a tsconfig or a jsconfig file

[typescript-bot]

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 or the TypeScript Discord community.

[jimmywarting]

is there a vscode setting for this?
or do i really need a tsconfig?

[TomasHubelbauer]

Since this is top Google hit for the error message, here is how you can get VS Code to chill about TLA when your runtime supports it (e.g.: Bun) and your IDE is holding you back - and all without the dreaded export {}:

tsconfig.json

{
  "compilerOptions": {
    "module": "ESNext",
    "moduleDetection": "force",
    "target": "ESNext"
  }
}