Missing coverage for Top Level Await
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 564
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 10
Description
There's a case where a TLA module and a non-TLA module both dynamically import the same TLA leaf-node module. This fails on JSC but passes on V8 and SM. So it looks like we are missing coverage in test262.
The minimal repro is attached to this bug report as a zip file.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached minimal reproduction and WebKit bug 242740, then inspect existing test262 coverage for dynamic imports involving top-level await. Done means adding a test that covers both a TLA and non-TLA module dynamically importing the same TLA leaf module and distinguishes the expected behavior across engines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100