Support TypeScript executable without extension when flag is set

What is the problem this feature will solve?

When I write an executable utility like build-game, I have to expose the implementation detail of the language it's written in, like build-game.ts.

#!/usr/bin/env node
// This file is named `build-game` not `build-game.ts`. Only plain JavaScript is allowed.

const foo: number = 1 // Error: TypeScript encountered.
console.log(foo)

/home/user/bin/build-game:3
const foo: number = 1
      ^^^

SyntaxError: Missing initializer in const declaration
    at wrapSafe (node:internal/modules/cjs/loader:1624:18)
    at Module._compile (node:internal/modules/cjs/loader:1666:20)
    at Object..js (node:internal/modules/cjs/loader:1824:10)
    at Module.load (node:internal/modules/cjs/loader:1427:32)
    at Module._load (node:internal/modules/cjs/loader:1250:12)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:235:24)
    at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:152:5)
    at node:internal/main/run_main_module:33:47

Node.js v24.4.1

What is the feature you are proposing to solve the problem?

When --experimental-strip-types is set (or add a new flag), force TypeScript evaluation. This will allow a script to encapsulate all interpreter detail.

#!/usr/bin/env -S node --experimental-strip-types
// This file is named `build-game` not `build-game.ts`. TypeScript is allowed
// because the `--experimental-strip-types` flag was passed.

const foo: number = 1
console.log(foo)

What alternatives have you considered?

If the executable is in an NPM package, I can just alias it in the package.json. If the executable is in my ~/bin, I can just shell alias it. However, these are both limited and really prevent me from sharing scripts with nice names that work everywhere.

The issue names no implementation files, entry points, or tests, so begin by locating Node's command-line flag handling and TypeScript execution behavior. Verify the desired behavior for an extensionless executable with --experimental-strip-types, including that existing extension-based behavior remains unchanged.