Config `importer` function returns wrong path when using ESM loader

[japa]

Config `importer` function returns wrong path when using ESM loader

[thetutlage]

Not a bug, the same needs to be written inside in an ESM project manually. We are doing it on all AdonisJS packages too.

Maybe, the create-japa initializer can generate the right code for bin/test.ts file

[thetutlage]

Added option for a TypeScript ESM project in the create-japa package. japa/create-japa@e05d09a

[Melchyore]

It seems that the importer function needs to return a path that starts with file:// (I don't know if it's a bug or intended). Solution below:

import { pathToFileURL } from "url";
import { assert } from "@japa/assert";
import { specReporter } from "@japa/spec-reporter";
import { runFailedTests } from "@japa/run-failed-tests";
import { processCliArgs, configure, run } from "@japa/runner";

configure({
  ...processCliArgs(process.argv.slice(2)),
  ...{
    files: ["tests/**/*.spec.ts"],
    plugins: [assert(), runFailedTests()],
    reporters: [specReporter()],
    importer: (filePath) => import(pathToFileURL(filePath).href), // ⬅ Here
  },
});

run();

@thetutlage Can you please confirm whether it's a bug or not?

[Melchyore]

Not a bug, the same needs to be written inside in an ESM project manually. We are doing it on all AdonisJS packages too.

Maybe, the create-japa initializer can generate the right code for bin/test.ts file

Thank you. I think it's also a good idea to add a note about this here: https://japa.dev/docs/usage-with-typescript#esm-projects