Step definations are not being inferred when using ESNext modules instead

[Himanshu21git]

Hello everyone,

I've been utilizing the Serenity/JS-Webdriverio-Cucumber JS template, which originally employed CommonJS modules as indicated in the tsconfig.json. As I transitioned some test scenarios to the main application source code, I encountered compatibility issues since the application follows the ESNext modules scheme. Although adding "type": "module" to my package.json resolved initial errors in wdio.conf.ts, I'm now facing challenges with the step definitions not being recognized. Consequently, when attempting to run the tests, I encounter implementation pending errors.

In my wdio.conf.ts file, I have configured cucumberOpts as follows:

cucumberOpts: {
    // <string[]> (file/dir) require files before executing features
    import: [
      "./features/support/*.ts",
      "./features/step-definitions/**/*.ts",
    ],
    // <string[]> (type[:path]) specify native Cucumber.js output format, if needed. Optionally supply PATH to redirect formatter output (repeatable)
    format: [],
    // <string> (name) specify the profile to use
    profile: "",
    // <boolean> fail if there are any undefined or pending steps
    strict: false,
    // <string[] | string> (expression) only execute the features or scenarios with tags matching the expression
    tags: [],
    // <number> timeout for step definitions
    timeout: 60000,
  },

Any guidance on resolving the issue would be highly appreciated.

Refer source code for reproduction.
@jan-molak

[Himanshu21git]

For the solution, please refer to this issue created by @jan-molak.

Moreover, the provided source code has been modified to address the mentioned issue.