This was an intended change, I believe. See related discussion: #18433

EDIT: Oh. Perhaps this is a legitimate bug because of the destructuring...? Not sure globals should be used/picked up in that location/syntax...

@AviVahl It's actually easier to trigger... please see the newly uploaded picture.

That's a different behavior, where a .ts file without any esm export/import statements is treated as a script. if you add export {} it would treat it as a module. Not to say that this is ideal behavior or anything.

Eventually, I assume we'll be able to look at an .mjs file and say "that's a module", but until then, this is an external behavior.

@DanielRosenwasser Just to add more info, .js is the same too:

This issue has been marked 'Working as Intended' and has seen no recent activity. It has been automatically closed for house-keeping purposes.