__filename is not defined

[casad1as]

ReferenceError: __filename is not defined when using latest @module-federation/modern-js-v3

Description

I am encountering a runtime error when starting a Modern.js application that uses the latest version of @module-federation/modern-js-v3.

The error is:

ReferenceError: __filename is not defined

This appears to happen inside the @module-federation/modern-js-v3 package, specifically around the usage of createJiti(__filename, ...).

I noticed that a related fix was merged in this PR:

#4784

However, the issue still persists after upgrading to the latest available version.

Error Output

file:///.../node_modules/@module-federation/modern-js-v3/dist/esm/cli/configPlugin.mjs:69
  jit = createJiti(__filename, {
                   ^

ReferenceError: __filename is not defined

Steps Tried

I have already tried the following:

1. Removed node_modules
2. Removed pnpm-lock.yaml
3. Reinstalled dependencies
4. Confirmed that the latest available version of @module-federation/modern-js-v3 is being used

Unfortunately, the same error still occurs.

Expected Behavior

The Modern.js dev server should start successfully without throwing a ReferenceError.

Actual Behavior

The dev server fails during startup because __filename is not available in the ESM context.

Additional Context

Since the error occurs in an .mjs file, it seems that __filename is still being referenced in an ESM environment where it is not defined by default.

Could you please confirm whether the fix from PR #4784 has been included in the latest published package version, or whether another release is needed?

Reproduction

Used Package Manager

pnpm

System Info

System:
    OS: Windows 11 10.0.26200
    CPU: (12) x64 AMD Ryzen 5 5600 6-Core Processor
    Memory: 4.17 GB / 15.93 GB
  Binaries:
    Node: 22.22.3 - C:\nvm4w\nodejs\node.EXE
    npm: 10.9.8 - C:\nvm4w\nodejs\npm.CMD
    pnpm: 10.34.1 - C:\nvm4w\nodejs\pnpm.CMD
  Browsers:
    Chrome: 149.0.7827.53
    Edge: Chromium (148.0.3967.83)

Validations

• Read the docs.
• Read the common issues list.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Module federation issue and not a framework-specific issue.
• The provided reproduction is a minimal reproducible example of the bug.

[2heal1]

let me fix it

[casad1as]

let me fix it

Hello @2heal1, thanks for your update!

I have updated to the latest available version, but the issue is still not resolved.

The previous issue related to ESM compatibility appears to persist in another form. The package is still executing CommonJS-specific APIs inside an ESM .mjs file.

Current error

ReferenceError: require is not defined
    at file:///.../node_modules/.pnpm/@module-federation+modern-j_ca63431ac87f90e75d71fc26bd25db9f/node_modules/@module-federation/modern-js-v3/dist/esm/cli/configPlugin.mjs:298:70
    at Object.call (.../@modern-js/plugin/dist/esm-node/hooks.mjs:68:34)
    at async init (.../@modern-js/plugin/dist/esm-node/cli/run/create.mjs:91:30)
    at async Object.run (.../@modern-js/plugin/dist/esm-node/cli/run/create.mjs:103:32)
    at async run (.../@modern-js/plugin/dist/esm-node/cli/run/run.mjs:16:5)
    at async run_run (.../@modern-js/app-tools/dist/esm-node/run/index.mjs:60:5)

Problematic code

Inside:

@module-federation/modern-js-v3/dist/esm/cli/configPlugin.mjs

The generated ESM file still contains:

resolve: {
  alias: {
    '@modern-js/runtime/mf': require.resolve('@module-federation/modern-js-v3/runtime')
  }
}

Because this file is emitted as .mjs, it is executed as an ES module. In that context, require is not available unless it is explicitly created with createRequire.

Expected behavior

The Modern.js v3 Module Federation plugin should run correctly in an ESM environment without throwing ReferenceError: require is not defined.

Actual behavior

The development server fails immediately during startup because configPlugin.mjs references require.resolve(...) directly.

Notes

This looks similar to the previous ESM compatibility issue where CommonJS globals were used inside ESM output. The update appears to have fixed or changed the earlier issue, but the package still contains another CommonJS reference inside the ESM build.

Could you please check the ESM build output for @module-federation/modern-js-v3, especially dist/esm/cli/configPlugin.mjs, and replace direct require.resolve(...) usage with an ESM-compatible approach?