Webpack bundle is missing the typescript worker

[lucat1]

monaco-editor version: 0.12.0
Browser: Any
OS: Any
Steps or JS usage snippet reproducing the issue:

Build the ESM example with webpack that can be found here

The error reported in the Devtools is about a missing package, but I beleive it is related to this webpack warning, and so to the issue #759.

[alexdima]

We have several fully working examples like e.g. here:
https://github.com/Microsoft/monaco-editor-samples/tree/master/browser-esm-webpack
https://github.com/Microsoft/monaco-editor-samples/tree/master/browser-esm-webpack-small
or here
https://github.com/Microsoft/monaco-editor-webpack-plugin#using

I'm sorry I cannot help you out with webpack specific questions, simply because I am not a webpack expert. I suggest to start with a sample.

[lucat1]

Indeed this issue is reproducible in the linked example. Tough I forgot to say you have to set the language to typescript. Try typing in the editor and errors shoud pop up.

[alexdima]

@lucat1 The sample works fine if you follow all the steps:

[flash-me]

For the Critical Dependency you can try this solution.
Regarding ts.Worker: Are you sure, that the specific workers have been built?

[youwenda]

https://github.com/Microsoft/monaco-editor-samples/tree/master/browser-esm-webpack

this example is OK because It satisfy HTML5 Worker Same Origin Policy, But If I place webpack bundle files in CDN.

Then in webpack.config.js may using __webpack_public_path__. eg:

self.MonacoEnvironment = {
	getWorkerUrl: function (moduleId, label) {
		if (label === 'json') {
			return __webpack_public_path__ + './json.worker.js';
		}
		if (label === 'css') {
			return __webpack_public_path__ + './css.worker.js';
		}
		if (label === 'html') {
			return __webpack_public_path__ + './html.worker.js';
		}
		if (label === 'typescript' || label === 'javascript') {
			return __webpack_public_path__ + './ts.worker.js';
		}
		return __webpack_public_path__ + './editor.worker.js';
	}
}

it will cause new Worker( ... ) run error and cause chrome console errors like this:

SO HOW TO SOLVE THIS PROBLEM?

[alexdima]

HTML5 does not allow to launch web workers from a different domain. In this case, you would need to have some piece of code that bootstraps things either inlined as base64 or in a .js on the same domain as the HTML.