[Bug]: TypeError: Cannot read properties of undefined (reading 'call')

[Sheetaa]

System Info

NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"

4.19.91-27.5.al7.x86_64

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 2
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 85
Model name: Intel(R) Xeon(R) Platinum 8269CY CPU @ 2.50GHz
Stepping: 7
CPU MHz: 2500.000
BogoMIPS: 5000.00
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 1024K
L3 cache: 36608K
NUMA node0 CPU(s): 0-3

Details

现象

页面打开时 js 报错白屏

排查原因

chunk 919874 引用了 chunk 588802，但是 588802 不存在，实际对应的 chunk id 的是 366421，chunk id 引用和提供的不一致

可以看下面搜索结果，正常情况下 chunk id 搜索结果至少有2个，1个定义，1个引用。而这2个 id 都只能搜出1个。588802只有引用，366421只有定义。

排查难点

尝试回滚到出问题的代码提交版本，重新编译部署（多次部署确认），问题没有复现，并且查看 chunk id 和出问题时候不一致。也就是后续的正常部署 chunk id 都是稳定的，只有出问题的那次 id 不同。
新部署的 id 如下：

环境信息

• Node.js：22.13.0
• Rspack：1.6.5
• Rspack 核心配置：

{
  output: {
    path: path.resolve(ROOT_PATH, `dist/${packageName}`),
    publicPath: cdnUrl,
    filename: (pathData) => {
      if (pathData.chunk.name === 'runtime') {
        return `[name].${version}.js`;
      }
      return '[name].[chunkhash:8].js';
    },
    chunkFilename: '[name].[chunkhash:8].js',
    crossOriginLoading: 'anonymous',
  },
  optimization: {
    minimizer: [
      new rspack.SwcJsMinimizerRspackPlugin({
        minimizerOptions: {
          // remove warnings
          warnings: isProdEnv,
          // Drop console statements
          drop_console: isProdEnv,
        },
        extractComments: false,
      }),
      new CssMinimizerWebpackPlugin(),
    ],
    runtimeChunk: {
      name: 'runtime',
    },
  }
}

moduleId 和 chunkId 没有专门设置，使用的默认值 'deterministic'

Reproduce link

No response

Reproduce Steps

无法重新编译复现，这是最奇怪的点

[github-actions[bot]]

Hello @Sheetaa, sorry we can't investigate the problem further without reproduction demo, please provide a repro demo by forking rspack-repro, or provide a minimal GitHub repository by yourself. Issues labeled by need reproduction will be closed if no activities in 14 days.

[JSerFeng]

We can't help without more info.

You can set optimization.moduleIds: 'named' and optimization.minimize: false to get more readable output so it can be more easy to debug

[Sheetaa]

We can't help without more info.

You can set optimization.moduleIds: 'named' and optimization.minimize: false to get more readable output so it can be more easy to debug

And also I already found the code in source which mapping to the error location. It's just a normal static import. I don't think the error caused by the import code internally.

[Sheetaa]

Like I mentioned above, I can't reproduce the bug even I used the same version code and the same deploy environment. Needless to say if I change the config settings to debug.
For this kind of issue, I'd prefer to start a discussion rather than jump straight to a solution. For example, what could be the possible reasons?

We can't help without more info.

You can set optimization.moduleIds: 'named' and optimization.minimize: false to get more readable output so it can be more easy to debug

[JSerFeng]

The core reason of such is that the module is not loaded yet when the code actually runs.

But in the reality, this is never gonna happen in the Rspack chunk loading algorithm, if it happens, it should be bug of Rspack. If you are loading chunks yourself instead of Rspack runtime, then you're likely to load all initial chunks before you start executing

[JSerFeng]

You can search 588802, it should be in another output files, and see what's the content of it

[Sheetaa]

I already did it. You can see it in my initial post.

[JSerFeng]

Nope, I mean search 588802 in your output folder, mostly /dist, not browser network or sources panel, it should be in other unloaded chunks

[Sheetaa]

Inspiring! I should search id in output dir. But another question is that I didn't reserve the static files in the non-reproducible problematic building output, originally for a smaller docker size. The static assets uploaded to CDN. Maybe I need to find another way to confirm this point.

[Sheetaa]

Finally, I found the reason by inspecting the files on CDN.
The chunk 78928 which report the error and the chunk 86438 which includes the referenced chunk are not belong to the same building output. Which is mean that chunk 86438 has the same file name(includes hash) but doesn't have the same file content between the two consecutive building outputs.
I rebuilt the two code versions and compared the chunk 86438, finally found that there's only one diff which I posted below:

The reason is that I used [chunkhash] for chunkFilename, not [contenthash]. Module id is not included into calculating the chunk hash in Rspack. However it acts not identical with what it acts in Webpack. I later found out that it was designed intentionally in Rspack, but I can't find any description about this on Rspack docs. The problem really bothered me for a long time. Maybe it should be highlighted in Rspack docs. Just a suggestion.