-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[💡 Feature]: ESM Compatibility #8306
Comments
With e970be9 we finalised the ESM transition of the core modules. It is not required for services and reporters to transition to ESM before the |
Well done ! |
Over the next days once the |
Is your feature request related to a problem?
Our goal for v8 is to deliver WebdriverIO packages for more than just Node.js environments. As a first step, let's make WebdriverIO ESM compatible (for that see
v8
branch). Next is to make all community packages compatible by moving them to ESM otherwise they can't be used in v8. The packages owned by this community are tracked here:Describe the solution you'd like.
Make sure that all packages are exported and published in way to be used using CJS and ESM.
Anyone who likes us to support in this effort, just pick one of the packages above and help transform them into ESM. You can follow this example commit to get a sense of what needs to be changed. Also this: https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c is a good resource.
Updates
it seems that the best tool to compile a hybrid modules isunbuild
, I am currently adding this build step to thev8
branch - the only problem is what to do with modules that only support ESMwebdriverio
,webdriver
anddevtools
packages we can just provide a CJS shim and import the ESM version too.Code of Conduct
The text was updated successfully, but these errors were encountered: