fix: Correctly handle absolute urls that start with a protocol

mod.js

@@ -286,7 +286,7 @@ function resolveImportsMatch(normalizedSpecifier, asURL, specifierMap) {
 			normalizedSpecifier.startsWith(specifierKey) &&
 			// * either asURL is null, or asURL is special
 			(!asURL ||
-				["ftp", "file", "http", "https", "ws", "wss"].includes(asURL.protocol))
+				["ftp:", "file:", "http:", "https:", "ws:", "wss:"].includes(asURL.protocol))
 		) {
 			// 1. If resolutionResult is null, then throw a TypeError indicating that resolution of specifierKey was blocked by a null entry.
 			if (resolutionResult === null) {

test/resolveModuleSpecifier.test.js

@@ -0,0 +1,19 @@
+import { assertEquals } from "asserts";
+import { resolveModuleSpecifier } from "../mod.js";
+
+Deno.test({
+	name: "resolveModuleSpecifier() with a https specifier",
+	fn() {
+		/** @type {import("../mod.js").ParsedImportMap} */
+		const parsedImportMap = {
+			imports: {
+				"https://example.com/": new URL("file:///foo/bar/"),
+			},
+		};
+
+		const baseUrl = new URL("file:///foo/script.js");
+
+		const result = resolveModuleSpecifier(parsedImportMap, baseUrl, "https://example.com/test.js");
+		assertEquals(result.href, "file:///foo/bar/test.js");
+	},
+});