> You'd still have to worry about config if you want to make adjustment and when that happens, the implicit smart defaults become a friction point.

In practice (when using tsx and when using a similar prececessor tech, esrun) ES moves forwards, not backwards.

Is your target "supported node.js and current browsers"? Today's tsx defaults work with that. They'll also work with tomorrows node.js and current browsers.