It only had std:blank, which we anticipate being specified as a built-in module that does nothing with no exports.
164 added std:blank/for-testing in order to test some cases. That's not going to be specified anywhere. But it seemed important to get that coverage.
This architecture is inelegant. Instead, the reference implementation should take a list of built-in modules as an argument to resolve(), and the tests should inject a list appropriate for their testing.
This is a low-priority code cleanup that I want to just write down while it is fresh in my mind.
Until recently the reference implementation has had a list of built-in modules as a hard-coded list:
https://github.com/WICG/import-maps/blob/da5665cb6ce03cbda7a9b9c68e8654b8d0fc757b/reference-implementation/lib/resolver.js#L5
It only had
std:blank
, which we anticipate being specified as a built-in module that does nothing with no exports.164 added
std:blank/for-testing
in order to test some cases. That's not going to be specified anywhere. But it seemed important to get that coverage.This architecture is inelegant. Instead, the reference implementation should take a list of built-in modules as an argument to
resolve()
, and the tests should inject a list appropriate for their testing.