Uh oh!
There was an error while loading. Please reload this page.
esm: import.meta.resolve exact module not found errors should return - #49038
Conversation
nodejs-github-bot
commented
Aug 6, 2023
Review requested:
|
guybedford
commented
Aug 6, 2023
@JakobJingleheimer wondering if you have any clues as to what might be up with this asan test failure here? |
Looking at the output, it seems all cases are reporting okay, which makes me think there's an async issue (something is not waiting as it should). No idea why this would be isolated to ASan. The test output appears to stop on: Loader hooks → should handle a throwing top-level body → should handle empty plain object
Ah, no, we know it's not because of I would guess something is unexpectedly throwing, and that's getting swallowed (and ESM worker would be the most likely suspect for swallowing it as we experienced that A LOT during the off-thread PR). I would still look here for the source of the unexpected throw node/lib/internal/modules/esm/initialize_import_meta.js Lines 22 to 25 in adee9bd |
GeoffreyBooth
commented
Aug 6, 2023
https://openjs-foundation.slack.com/archives/C053UCCP940/p1690842970936839:
From July 31, so this might’ve been introduced by one of the earlier recent loaders PRs. cc @izaakschroeder |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This resolves#49010, ensuring that not found errors to exact modules in
import.meta.resolvestill return the resolved string. Package not found errors remain module not found errors.@nodejs/modules