[Bug]: serving wasm after using Copy

[sedghi]

Version

System:
    OS: macOS 15.3.2
    CPU: (24) arm64 Apple M2 Ultra
    Memory: 369.77 MB / 128.00 GB
    Shell: 5.9 - /bin/zsh
  Browsers:
    Chrome: 134.0.6998.166
    Chrome Canary: 136.0.7101.0
    Edge: 134.0.3124.95
    Safari: 18.3.1

Details

I'm using the onnxruntime library, which has wasm dependencies. To make it work with Webpack, I needed to add the following to my Webpack configuration:

new CopyWebpackPlugin({
        patterns: [
          {
            from: '../../../node_modules/onnxruntime-web/dist',
            to: DIST_DIR,
          },
]})

This puts all the wasm files ready to be served, which I can confirm by checking localhost:3000/webpack-dev-server.

The files are requested from http://localhost:3000/ort-wasm-simd.jsep.wasm, and everything works as expected.

---

However, when using Rsbuild, after doing the similar copy via:

output: {
    copy: [
      {
        from: path.resolve(__dirname, 'node_modules/onnxruntime-web/dist'),
        to: DIST_DIR,
      },

and verifying they are served at http://localhost:3000/rsbuild-dev-server:

For some reason, the files are now being requested from http://localhost:3000/static/js/async/ort-wasm-simd.jsep.wasm.

Reproduce link

N/A

Reproduce Steps

It's kind of hard to reproduce this outside of my package. I'm hoping to get some answers before I create a reproduction link.

[chenjiahan]

This looks like a bug, a reproduction link would be helpful

[github-actions]

Hello @sedghi. Please provide a reproduction repository or online demo. For background, see Why reproductions are required. Thanks ❤️

[sedghi]

Sure, i will create a reproduction link soon