-
-
Notifications
You must be signed in to change notification settings - Fork 729
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
Migrate CodeceptJS to ESM (Top-level await) #4185
Labels
Comments
@danielhelen at this moment this means to rewrite CodeceptJS completely and I don't think we have enough resources to handle this task. |
Actually we can try this codemod, which can make migration faster |
DavertMik
changed the title
Top-level await
Migrate CodeceptJS to ESM (Top-level await)
Feb 17, 2024
#4229 We are working on it! |
This issue is stale because it has been open for 90 days with no activity. |
Do we have any target date for #4229 ? |
Hi @kobenguyent @DavertMik ... any ETA for this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What are you trying to achieve?
I need to use top-level
await
to retrieve config from AWS and other APIs but CodeceptJS seems completely incompatible with ES modules. Top-level await is simply not possible in CommonJS. Are there any plans to support ES modules?What do you get instead?
If you set
"type": "module"
inpackage.json
you get this error:Details
The text was updated successfully, but these errors were encountered: