[Bug] regular webpack does not work to resolve workers

[xilin22]

Reproducible in vscode.dev or in VS Code Desktop?

• Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

• Not reproducible in the monaco editor playground

Monaco Editor Playground Code

No response

Actual Behavior

I was following this example (https://github.com/microsoft/monaco-editor/tree/main/samples/browser-esm-webpack-typescript-react) to create a Monaco component in my app. I keep getting the errors noted in the image.

When I created this locally on my computer everything worked as expected.

However, when implementing monaco editor into my project, I see the error in the image that I have posted. When I changed to use the MonacoWebpackplugin rather than the HtmlWebPackPlugin in the webpack.config.js, the errors are gone.

It is important to note that, despite there now being any errors in my console, my diff editor is not highlighting the differences between the 2 files.

The following are the changes that I made to the webpack.config.js in the example to resolve this issues that were in the console.

//The webpack.config.js file

const path = require("path");
// const HtmlWebPackPlugin = require("html-webpack-plugin");
const MonacoWebpackPlugin = require("monaco-editor-webpack-plugin");
const ReactRefreshWebpackPlugin = require("@pmmmwh/react-refresh-webpack-plugin");

...

plugins: [
    // new HtmlWebPackPlugin({
    //  template: "src/index.html",
    // }),
    new MonacoWebpackPlugin(),
    isDevelopment && new ReactRefreshWebpackPlugin(),
  ].filter(Boolean),

...

Expected Behavior

I'd expect that when the Monaco component is integrated into my app (component create results in no issues), it would automatically calculate and highlight the differences between files being compared in the diff editor --- unless what I am expecting is wrong/ not how the diff editor works.

Additional Context

I was also suggested to add these points to help with troubleshooting.
• The minimal webpack config to reproduce this issue
• Network errors or any error in the Dev Tools