Add a tsconfig option to assume every .ts file is a module

[osyrisrblx]

Currently with TypeScript, if I create two files and put const foo = "bar"; in each, I will get the following error:

For the specific environment I'm using, this is not the case at runtime. I'd like to silence this error with a tsconfig.json option.

One current workaround is to put export {}; in all my files to instruct TypeScript that the file is a module, but I'd like to avoid doing so.

[osyrisrblx]

More info about workaround found here:
https://stackoverflow.com/questions/40900791/cannot-redeclare-block-scoped-variable-in-unrelated-files

[RyanCavanaugh]

Duplicate of #18232

[osyrisrblx]

@RyanCavanaugh Any chance of a tsconfig.json option to force all files to be considered modules?

My project does not run in a standard environment and files never share scope. Having to put export {} at the top of every file is frustrating.