[Bug]: Cannot execute the defineConfig function in a Jest test

[patricklafrance]

Version

System:
    OS: Windows 11 10.0.22631
    CPU: (20) x64 13th Gen Intel(R) Core(TM) i7-13700H
    Memory: 9.70 GB / 31.62 GB
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    @rsbuild/core: 1.1.8 => 1.1.8

Details

When executing the defineConfig function in a Jest test, I get the following error:

TypeError: The argument 'filename' must be a file URL object, file URL string, or absolute path string. Received 'http://localhost/main.js'

The code under test:

import { defineConfig } from "@rsbuild/core";

export function myDefineConfig() {
    return defineConfig({});
}

The test:

import { myDefineConfig } from "../src/myDefineConfig.ts";

test("my test", () => {
    const config = myDefineConfig();

    expect(config).toMatchSnapshot();
});

I found this example which inspired most of my reproduction configs. It seems like something changed since this example has been created.

Reproduce link

https://github.com/patricklafrance/rsbuild-jest

Reproduce Steps

• pnpm install
• pnpm test

[chenjiahan]

Rslib generates the following code and it breaks Jest + JSDom:

let __rslib_import_meta_url__ = 'undefined' == typeof document ? new (require('url'.replace('', ''))).URL('file:' + __filename).href : document.currentScript && document.currentScript.src || new URL('main.js', document.baseURI).href;

[chenjiahan]

@patricklafrance I think you should remove testEnvironment: "jsdom" from your Jest config file because you are testing a Node.js library, not a client library.

[patricklafrance]

@chenjiahan oh that's embarrassing, indeed removing testEnvironment: "jsdom" fix the issue. Too much copy paste 😓

Should I leave this issue open since it doesn't work with testEnvironment: "jsdom" and the other issue you mentionned?

[chenjiahan]

Never mind 😄

We should check whether the output of Rslib is reasonable and then decide whether to close this issue.

[fi3ework]

@rsbuild/core is not supposed to run in browser, and the current shim implementation of import.meta.url is aligned with Rollup which is widely adopted. Closing for not gonna change the shim.