See denoland/deno#14243. Imagine side-effect-importing some polyfill from esm.sh at your application entrypoint. That polyfill was built for Deno to import things from std/node. If it is asynchronously evaluated, you will get an undesired dependency evaluation order and the conventional import "https://cdn.esm.sh/reflect-metadata?deno" at your application entrypoint might not suffice.

In this case there is a single easily fixed culprit: https://github.com/denoland/deno_std/blob/8824ae1ef3e53a6531b464f9add1eb40a60b9d64/node/internal/util/debuglog.ts#L108-L113

cc @shivam-tripathi