Closed
Description
Version
v20.0.0
Platform
Darwin Bumbles-MBP.home 21.6.0 Darwin Kernel Version 21.6.0: Thu Mar 9 20:08:59 PST 2023; root:xnu-8020.240.18.700.8~1/RELEASE_X86_64 x86_64
What steps will reproduce the bug?
- clone this repo or download this package
- run
npm testfrom the cloned or unpacked package - see the error
Essentially, using --loader and await import('./path/to/module.js') from inside any imported module causes the test to fail for no reason related to the test or any of the files used.
A copy of the error seen in the test process is attached here
testnode$ npm test
> test
> node --experimental-loader=./anyloader.js --test
ℹ (node:55506) ExperimentalWarning: Custom ESM Loaders is an experimental feature and might change at any time
ℹ (Use `node --trace-warnings ...` to show where the warning was created)
✖ should not show promise resolution error (3.975453ms)
Error: Promise resolution is still pending but the event loop has already resolved
at process.emit (node:events:523:35)
ℹ tests 1
ℹ suites 0
ℹ pass 0
ℹ fail 0
ℹ cancelled 1
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 8.432653
ℹ THIS CONSOLE LOG IS PREINTED
ℹ tests 1
ℹ suites 0
ℹ pass 0
ℹ fail 0
ℹ cancelled 1
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 150.112342
✖ failing tests:
✖ should not show promise resolution error (3.975453ms)
Error: Promise resolution is still pending but the event loop has already resolved
at process.emit (node:events:523:35)How often does it reproduce? Is there a required condition?
The issue is reproduced every time on this machine, using the package attached above
What is the expected behavior? Why is that the expected behavior?
The test in the attached package should pass without any error, following the behaviour of previous versions of node from v12 onward.
What do you see instead?
Error: Promise resolution is still pending but the event loop has already resolvedIn the example failing test, the test process reaches the passing condition but the test fails regardless