7 ms·

I don't think it's accurate to say "without worrying about configuration". The next line is more accurate: > tsx runs your TypeScript code with modern and sens

I don't think it's accurate to say "without worrying about configuration". The next line is more accurate: > tsx runs your TypeScript code with modern and sensible defaults, making it user-friendly and especially great for beginners. 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. It might also surprise you with errors when you attempt to bundle the code. It'd be nice to have tsx available at runtime so I can run TypeScript code without worrying about the transpiler

nailer 1y ago
> 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.
- keysdev 1y ago
  esno seems a better alternative. esbulit has already solve much of that for devs.
  - Quarrel 1y ago
    esno is now tsx, from their github: > From v0.15, esno is essentially an alias of tsx, with automated CJS/ESM mode and caching. and all issues are now filed in the tsx repo.