Artillery fails to execute tests when 'type: module' is set in package.json despite ESM support

[davidjjohn97]

Issue:
Identified a compatibility issue in Artillery where it fails to properly handle ESM modules when "type": "module" is specified in package.json, despite claiming ESM support. The error manifests as "module is not defined" during test compilation, forcing users to maintain separate package configurations for Artillery tests. This impacts projects trying to standardize on ESM modules and requires additional configuration management to work around.

Version info: <2.0.22>

<version>

Running this command:

artillery run load-test.ts

I expected to see:
Artillery to properly handle ESM modules when "type": "module" is specified in package.json, since Artillery documentation claims ESM support.

Instead, this happened:
Received ReferenceError: module is not defined at dist/gismo-load-test.ts:26:1, indicating Artillery's compiler is not properly handling ESM module syntax when "type": "module" is set in package.json.

Current workaround: Created a separate package.json without "type": "module" specifically for Artillery tests.

Stack trace shows the error occurs during module compilation: