206 Partial Content returning unfinished response of vendor-node_modules. Potential config issue between React MFE and Next Js Application?

[jlecadent]

Hello! I am relatively new to Webpack MFE configurations so please bare with me,

Context:
So currently I have two separate applications repositories that each have a webpack config file, one is a MFE that is built with React js and the other is built with Next Js. The Next JS app will be consuming the remote entry of the React MFE. Snippets of the config files are shown below

React App Config file:

    {
      name: "reactAppMFE",
      filename: "remoteEntry.js",
      exposes: {
        "./reactMFE": "./src/app/features/index.jsx",
      },
      shared: {
        react: {
          singleton: true,
          requiredVersion: deps.react,
        },
        "react-dom": {
          singleton: true,
          requiredVersion: deps["react-dom"],
        },
      },
    },

Next JS App Config file:

         {
            name: 'host',
            remotes: {
              reactAppMFE: `reactAppMFE@https://my-example-live-app.com/remoteEntry.js`,
            },
            filename: 'static/chunks/remoteEntry.js',
            shared: {},
            exposes: {},
            library: { type: 'var', name: 'host' },
          }

The Issue
When I'm pointing each application to one another within localhost using the webpack dev server, the Next Js app is able to use the remoteEntry.js file associated with the React App MFE and has no issues what so ever. Now when it comes to having both applications hosted on a IIS Web Server I would sometimes get an intermitting 206 partial content syntaxError response from one of the static javascript vendor-node_modules files from React MFE app

Example below of the following vendor-node_modules js errors when viewing the syntax error:

When I compare the 206's that throws a syntaxError vs 206's that don't throw any syntaxError, there doesn't seem to be any weird outstanding differences within the request header and when I refresh the applications it works as expected. During certain initialization of the React MFE and Next JS app when the issue does occur it, seems like the error only happens to one out of the many vendor-node_module bundle js files regardless of size. There isn't a single vendor-node_modules bundle js file that is always failing but rather a different one each time the error occurs.

The Question:
Based on the webpack configurations i posted above, I am missing anything that could be causing this intermitting issue on a hosted server?

I know that webpack out of the box supports ES Module and Common JS Module so i feel like its not a difference in build issue between the Next js App and the React MFE App since its intermitting but I could be wrong. This issue can very much be solely my ISS server configurations, however I'm trying to rule out if theres any misconfigurations in my webpack configs to further debug this issue I'm facing

If you need more information please feel free to ask!

Thank you guys, any help is greatly appreciated!