Endo: Distinguish "dependency" from "dependency/" module specifiers

[kriskowal]

A name like "dependency" will first match a built-in, if available, and fall back to an explicit dependency from package.json. A name like "dependency/" will strictly use the dependency from package.json.

[kriskowal]

If this comes up again, I would prefer to send an upstream change to prefer the new convention to distinguish node:fs from fs instead of fs from fs/.

Do remind me if a case like this comes up again. I’m closing on the grounds that I prefer not to imagine us emulating this behavior by the only means I can imagine: Adding / suffixes to the canonical module specifier.