bug: The 'import.meta' meta-property is only allowed when the...

[gajus]

Node.js version

22

NPM version

10

@checkly/cli version

0.4.14

Steps to reproduce

1. Use import.meta.dirname
2. Run pnpx checkly test

What is expected?

For tests to run.

What is actually happening?

The 'import.meta' meta-property is only allowed when the '--module' option is 'es2020', 'es2022', 'esnext', 'system', 'node16', or 'nodenext'.
entrypoint: path.join(import.meta.dirname, 'homepage.spec.ts')

Our tsconfig.json already uses nodenext, so it is not clear where it is picking up the other value.

Any additional comments?

No response

[sorccu]

Hi @gajus,

I just tried it out myself and can confirm that the issue is real. The cause seems to be that we load any check files with .ts extension using ts-node here:

checkly-cli/packages/cli/src/services/util.ts

Lines 96 to 104 in df80080

	const tsNode = await import('ts-node')
	tsCompiler = tsNode.register({
	moduleTypes: {
	'**/*': 'cjs',
	},
	compilerOptions: {
	module: 'CommonJS',
	},
	})

As you can see it's setting module: 'CommonJS' in there, as well as forcing all moduleTypes to cjs.

To be honest I am not quite sure why it's doing that. It seems that it has always been like that, ever since it was added in #298. Some useful context can also be found in #804.

I will try to uncover some additional context about the reasoning behind this whole thing next week and figure out if we can change it.

Thanks for the report!

[gajus]

Can you just use something like tsx?

The latter is a lot more lenient with its inputs.