There are cases where the specifier is mapped to a different alias by the module loader.
In this case, the waker for the future that resolves the module in the upstream codebase may not be properly registered, causing the module resolution phase to hang indefinitely.
This upstream bug has been fixed in denoland/deno_core#762, but since we don't plan to version up the Deno codebase yet, we decided to fork and cherry-pick that PR.
What kind of change does this PR introduce?
Bug fix
Description
There are cases where the specifier is mapped to a different alias by the module loader.
In this case, the waker for the future that resolves the module in the upstream codebase may not be properly registered, causing the module resolution phase to hang indefinitely.
This upstream bug has been fixed in denoland/deno_core#762, but since we don't plan to version up the Deno codebase yet, we decided to fork and cherry-pick that PR.
Related supabase/supabase#26840