davidot 1dc9769f7d LibJS: No longer assume there is a cycle root when module failed before ...

This issue could be triggered by evaluating a module twice. If it failed
during evaluation the cycle root was never set but that status is
evaluated. This failed in step 3 of Evaluate which assumes it has a
cycle root. This is a spec issue see:
https://github.com/tc39/ecma262/issues/2823

To fix this we check if the module itself has a top level capability
first before going to the cycle root.

Co-authored-by: Jamie Mansfield <jmansfield@cadixdev.org>

2022-11-27 00:51:36 +00:00

28 KiB

Raw Blame History

View Raw