Turbopack / next.js 16

[kaisalmen]

Hi @CGNonofr have your used this stack already with Next.js 16 where Turbopack is now the default?
Turbopack does not like the Textmate tokenizer:

and also fails to load the worker based extension host when using @codingame/monaco-vscode-typescript-language-features-default-extension.

So far, I have not found a way to fix it, but I am investigating right now. Any ideas are welcome. 🙂

Problems can be reproduced on this branch: https://github.com/TypeFox/monaco-languageclient/tree/nextjs-16

Edit: I swapped the images as they were in the wrong order.

[CGNonofr]

Hi!

Just had a look

Turbopack does not like the Textmate tokenizer:

There is a new URL('vscode-oniguruma/release/onig.wasm', import.meta.url).href in the code, and for some reasons, turbopack transform it to a path only (without url) and that's the issue, didn't find a way in the config to st a baseUrl or something 🤔

and also fails to load the worker based extension host when using @codingame/monaco-vscode-typescript-language-features-default-extension.

It seems turbopack doesn't support workers very well, at least doesn't support the new Worker(new URL('...', import.meta.url)), so it just considers the worker file as an asset and doesn't resolve imports in it

[kaisalmen]

It seems turbopack vercel/turborepo#3643,

Yes, I can confirm that. For workers you have in your app/under your control you can pre-bundle them, but when things happen in your dependencies you are stuck.

didn't find a way in the config to st a baseUrl or something 🤔

It seems not very configurable. At least that is my impression when I looked at the docs

[kaisalmen]

@CGNonofr hopefully the way out can be to pre-bundle everything not next related with Rolldown and then use the artifact. I will try that on the branch above...

[CGNonofr]

I don't see any other solution either! except forcing webpack instead of turbopack ofc