Update to monaco-vscode-api 3.2.1

[kaisalmen]

Using the standalone packages from monaco-editor works. Transformation of workers to esm bundles also works fine. Loading the workers directly via the factory function does not. I don't understand yet why. Editor worker is no problem.

[CGNonofr]

What is the errors with the workers?

[kaisalmen]

@CGNonofr first, one guy called Kai is unable to type properly. Then vite gets confused if you specify this (js extension):

typescript: () => new Worker(new URL('@codingame/monaco-vscode-standalone-typescript-language-features/worker.js', import.meta.url), { type: 'module' })

instead of this:

typescript: () => new Worker(new URL('@codingame/monaco-vscode-standalone-typescript-language-features/worker', import.meta.url), { type: 'module' })

It is now working.

[CGNonofr]

@CGNonofr first, one guy called Kai is unable to type properly. Then vite gets confused if you specify this (js extension):

typescript: () => new Worker(new URL('@codingame/monaco-vscode-standalone-typescript-language-features/worker.js', import.meta.url), { type: 'module' })

instead of this:

typescript: () => new Worker(new URL('@codingame/monaco-vscode-standalone-typescript-language-features/worker', import.meta.url), { type: 'module' })

Yep, that's because as soon as you have an exports field in your package.json, you can't import any other file directly. It's not really a vite specificity. What is specific to vite is that if the url of the worker can't be resolved, it just gives up transforming it without errors.

So everything is fine now?

[kaisalmen]

What is specific to vite is that if the url of the worker can't be resolved, it just gives up transforming it without errors.

It says the file is not there and that is just not true. It has no visibility due to the extra export. I like that you did that actually.

So everything is fine now?

Yes

[kaisalmen]

@CGNonofr I disabled the yarn verification in the CI. It is making trouble all the time because it can't resolve local dependencies.

[kaisalmen]

@CGNonofr this is now really ready.