ownname.test.ts

import assert from "assert";
import { type Scenario, mapDirectory, runScenarios } from "./scenarios";

const filesOwnName = await mapDirectory("test/fixtures/scenario_ownname");

const scenarios: Scenario[] = [
  {
    files: filesOwnName,
    commands: ["jspm install app"],
    validationFn: async (files: Map<string, string>) => {
      // Installing the own-name package "app" should result in the version of
      // es-module-lexer in the import map being upgraded to 1.2.2, since it's a
      // transitive dependency of "./app.js".
      const map = JSON.parse(files.get("importmap.json"));
      assert(
        map?.imports?.["es-module-lexer"]?.includes("es-module-lexer@1.3.0")
      );
    },
  },
  {
    files: filesOwnName,
    commands: ["jspm link ./app.js -o outputmap.json"],
    validationFn: async (files: Map<string, string>) => {
      // Tracing the local module ./app.js should result in a top-level import
      // of es-module-lexer@0.10.5, as that is the version in the input map,
      // even though the package.json has a version constraint of ^1. This is
      // because we treat the input map as a lockfile:
      const map = JSON.parse(files.get("outputmap.json"));
      assert(
        map?.imports?.["es-module-lexer"]?.includes("es-module-lexer@0.10.5")
      );
    },
  },
  {
    files: filesOwnName,
    commands: ["jspm link app -o outputmap.json"],
    validationFn: async (files: Map<string, string>) => {
      // If we trace the own-name package "app" instead, we should get the same
      // result, as the package.json has an export for "app" -> "./app.js":
      const map = JSON.parse(files.get("outputmap.json"));

      // TODO: once we fully implement re-entrant primary scope in the generator
      // we should be able to check map.imports rather:
      assert(
        map?.scopes?.["./"]?.["es-module-lexer"]?.includes(
          "es-module-lexer@0.10.5"
        )
      );
    },
  },
];

runScenarios(scenarios);