We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Support top-level-await
This lets await being called in the top scope of a module (not a commonjs script).
await
Allowing users to use k6/experimental/fs.open and others in the init context more ergonomically
k6/experimental/fs.open
This was skipped in #3456 as it required even more changes to the initial loading as it now needs to be 100% asynchronous.
Sobek already supports this, so this will likely mostly be changing signatures inside k6 in js and js/modules
js
js/modules
No response
The text was updated successfully, but these errors were encountered:
Mentioning it for context: #3743 (comment)
Sorry, something went wrong.
mstoykov
Successfully merging a pull request may close this issue.
Feature Description
Support top-level-await
This lets
await
being called in the top scope of a module (not a commonjs script).Allowing users to use
k6/experimental/fs.open
and others in the init context more ergonomicallySuggested Solution (optional)
This was skipped in #3456 as it required even more changes to the initial loading as it now needs to be 100% asynchronous.
Sobek already supports this, so this will likely mostly be changing signatures inside k6 in
js
andjs/modules
Already existing or connected issues / PRs (optional)
No response
The text was updated successfully, but these errors were encountered: