Error: tsx must be loaded with --import instead of --loader

[dangnhdev]

node:internal/process/esm_loader:40
      internalBinding('errors').triggerUncaughtException(
                                ^
Error: tsx must be loaded with --import instead of --loader
The --loader flag was deprecated in Node v20.6.0
    at V (file:///project/node_modules/tsx/dist/esm/index.mjs:1:1956)
    at Hooks.addCustomLoader (node:internal/modules/esm/hooks:178:24)
    at Hooks.register (node:internal/modules/esm/hooks:144:16)
    at async initializeHooks (node:internal/modules/esm/utils:184:5)
    at async customizedModuleWorker (node:internal/modules/esm/worker:86:24)

Node.js v20.9.0

I've just tried this new plugin and got this error. The file run without error with old plugin.

[Lordfirespeed]

I think this is partially due to changes in Node.js and TSX rather than this plugin, but I should be able to implement a fix!

[Lordfirespeed]

After some investigation ...

• --import is available in all versions of Node >=18.18.0
  • (unimportant) it is preferable in Node >=18.19.0, <19 and Node >=20.6.0, which include nodejs/node@a40a6c8, nodejs/node@6ad8318 and nodejs/node@a2fc4a3
• For versions of Node <18.18.0, --import is not available so --loader (which is an alias for --experimental-loader) must be used

So, to resolve this issue -

• When Node version >=18.18.0, use --import over --require in all possible scenarios
  • check for compatability with ts-node
  • check for compatability with esno and tsx
• When Node version <18.18.0, use --require in all possible scenarios

[nullice]

Perhaps you can provide an option directly

[Lordfirespeed]

Perhaps you can provide an option directly

Yes, that's my intention. I haven't got round to it. Feel free to contribute :)