[🐛 Bug]: Better detection of config files

[nextlevelbeard]

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

WebdriverIO Extension Version

latest

WebdriverIO Version

latest

Node.js Version

20

Which capabilities are you using?

What happened?

A file that is inside a project sub-folder / workspace will not be detected.
A file that is not named exactly "wdio.conf.[jt]s" will not be detected.

Users might have a need for different file names to differentiate them (cloud.conf.ts, local.conf.ts, etc)

What is your expected behavior?

A file that is inside a project sub-folder / workspace is detected.
A file that is not named exactly wdio.conf.[jt]s is detected but ending in ".conf.[tj]s" is detected.

How to reproduce the bug.

Relevant log output

-

Code of Conduct

• I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues

[mato533]

@nextlevelbeard
Thank you for reporting.
This is bug of the default value of configuration for this extension...

I will fix it and release new version ASAP.

UPDATE

The default value for the setting of this extension was set wrong, so it was corrected and released. This allows for more flexible filenames to be supported in the standard, although the string wdio and conf must be included in the configuration filename.

[mato533]

@nextlevelbeard

A file that is inside a project sub-folder / workspace is detected.

This is supported. the extension can detect subfolder not only root folder.

A file that is not named exactly wdio.conf.[jt]s is detected but ending in ".conf.[tj]s" is detected.

Considering the possibility that other libraries may have configuration files like *.conf.[tj]s (e.g. karma.conf.ts``,webpack.dev.conf.js), we have added the configuration to enable the extension when a file matching **/* wdio*.conf*. {ts,js,mjs,cjs,cts,mts}.　I think we should avoid enabling this extension unnecessarily, what do you think?

[mato533]

Other similar extension are activated only when the workspace has their configuration files.

• Jest
• Vitest
• Playwright

So, basically, we are going to keep the current implementation. Any feedback would be appreciated.