triggerUncaughtException: Error: tsx must be loaded with --import instead of --loader is received after upgrading to v9 #13664

jurjandrei · 2024-09-27T09:27:05Z

jurjandrei
Sep 27, 2024

Hello,

I am trying to upgrade to v9 and getting this error:

My tsconfig.json looks like this:

{ "compilerOptions": { "target": "ES2017", "module": "ESNext", "moduleResolution": "node", "noImplicitAny": false, "esModuleInterop": true, "allowJs": false, "strict": false, "lib": [ "ESNext", "dom" ], "skipLibCheck": true, "outDir": "dist", "rootDir": ".", "allowSyntheticDefaultImports": true, "types": [ "node", "@wdio/globals/types", "@wdio/mocha-framework", "@wdio/appium-service" ], "noEmit": false, "forceConsistentCasingInFileNames": true }, "include": [ "./**/*.ts" ], "exclude": ["node_modules"], "ts-node": { "files": true } }

I have also in package.json "type": "module"

Can someone guide me on how to fix it? Thanks

Answered by jenskuhrjorgensen

Oct 16, 2024

@christian-bromann sure, here it is:
#13768

View full answer

christian-bromann · 2024-09-27T16:02:54Z

christian-bromann
Sep 27, 2024
Maintainer

@jurjandrei can you provide a minimal reproducible example?

2 replies

jurjandrei Sep 29, 2024
Author

@christian-bromann I just updated the version of "@wdio/cli": from 8.40.2 to 9.1.1 and then the error was received when trying to start a test.

jurjandrei Sep 29, 2024
Author

yarn test
yarn run v1.22.22
$ cross-env wdio $npm_package_config_CONFIG_PATH --suite $npm_package_config_SUITE

node:internal/modules/run_main:125
    triggerUncaughtException(
    ^
Error: tsx must be loaded with --import instead of --loader
The --loader flag was deprecated in Node v20.6.0 and v18.19.0
    at initialize (file:///Users/****/****/****/node_modules/tsx/dist/esm/index.mjs:1:919)
    at Hooks.addCustomLoader (node:internal/modules/esm/hooks:181:24)
    at Hooks.register (node:internal/modules/esm/hooks:155:16)
    at async initializeHooks (node:internal/modules/esm/utils:317:5)
    at async customizedModuleWorker (node:internal/modules/esm/worker:109:13)

Node.js v22.0.0
error Command failed with exit code 1.

CJskii · 2024-09-28T10:02:25Z

CJskii
Sep 28, 2024

@jurjandrei I believe this issue is caused by your node version.

Update tsx to the latest version and use at least node 20

1 reply

jurjandrei Sep 29, 2024
Author

@CJskii I am using the latest typescript version and also node 22.

soudai-s · 2024-10-13T02:09:25Z

soudai-s
Oct 13, 2024

Hi, I've been encountered the same issue and resolve that to use v8.40.6 of @wdio/cli instead of v9.1.5.

node -v
v22.4.0

0 replies

daganilsen · 2024-10-15T06:54:30Z

daganilsen
Oct 15, 2024

Hi. I have the same issue using node 22.1.0 and @wdio/cli 9.2.1
Any news on this?
Thanks!

Executing test with:
npm run TestX

node:internal/modules/run_main:125
triggerUncaughtException(
^
Error: tsx must be loaded with --import instead of --loader
The --loader flag was deprecated in Node v20.6.0 and v18.19.0
at initialize (file:///C:/Projects/xyz/node_modules/tsx/dist/esm/index.mjs:1:919)
at Hooks.addCustomLoader (node:internal/modules/esm/hooks:181:24)
at Hooks.register (node:internal/modules/esm/hooks:155:16)
at async initializeHooks (node:internal/modules/esm/utils:317:5)
at async customizedModuleWorker (node:internal/modules/esm/worker:109:13)

0 replies

jenskuhrjorgensen · 2024-10-16T08:53:38Z

jenskuhrjorgensen
Oct 16, 2024

I think the issue lies within this line:

const moduleLoaderFlag = (
                (runCmd.nodeVersion('major') >= 20 && runCmd.nodeVersion('minor') >= 6) ||
                (runCmd.nodeVersion('major') === 18 && runCmd.nodeVersion('minor') >= 19)
            )
                ? '--import'
                : '--loader'

webdriverio/packages/wdio-cli/tests/commands/run.test.ts

Line 132 in 06a7c8c

(runCmd.nodeVersion('major') >= 20 && runCmd.nodeVersion('minor') >= 6) ||

If you are running e.g. Node 21 or 22 on a minor version that is below 6, then it will set moduleLoaderFlag to --loader instead of --import. I think the intention with the code was that it would set it to --import for all versions >= 20.6, but that is not what it does.

I bumped my Node version from 22.3 to 22.9 and now I'm no longer getting the Error: tsx must be loaded with --import instead of --loader error.

10 replies

christian-bromann Oct 16, 2024
Maintainer

Great discovery! Mind raising a PR with a fix for this?

jenskuhrjorgensen Oct 16, 2024

@christian-bromann sure, here it is:
#13768

Answer selected by christian-bromann

christian-bromann Oct 16, 2024
Maintainer

Thanks for your investigation and resolving the problem. I hope to release wdio tomorrow.

avinash1406 Oct 20, 2024

HI @christian-bromann ,
Today, I have freshly installed WDIO on my machine. However, when I try to run the tests, I receive the following error. It seems this issue is still not resolved. What can be done locally to fix this problem? Please let us know.

christian-bromann Oct 20, 2024
Maintainer

What can be done locally to fix this problem?

Can you update to the latest Node.js v20.x version?

avinash1406 Oct 20, 2024

It's having updated version 23

Do I have to downgrade it to 20 ?

Uh oh!

triggerUncaughtException: Error: tsx must be loaded with --import instead of --loader is received after upgrading to v9 #13664

Uh oh!

Replies: 5 comments · 13 replies

Uh oh!

christian-bromann Sep 27, 2024 Maintainer

Uh oh!

jurjandrei Sep 29, 2024 Author

Uh oh!

jurjandrei Sep 29, 2024 Author

Uh oh!

Uh oh!

jurjandrei Sep 29, 2024 Author

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

christian-bromann Oct 16, 2024 Maintainer

Uh oh!

Uh oh!

christian-bromann Oct 16, 2024 Maintainer

Uh oh!

Uh oh!

christian-bromann Oct 20, 2024 Maintainer

Uh oh!

Uh oh!

Replies: 5 comments 13 replies

christian-bromann
Sep 27, 2024
Maintainer

jurjandrei Sep 29, 2024
Author

jurjandrei Sep 29, 2024
Author

jurjandrei Sep 29, 2024
Author

christian-bromann Oct 16, 2024
Maintainer

christian-bromann Oct 16, 2024
Maintainer

christian-bromann Oct 20, 2024
Maintainer