Behavior differences between v15.0.3 and v16.1.0

[Nuthin2do]

Hi,

i have noticed the following behavior:

In our soultion we have this piece of code:

import {
  editor,
  Uri,
  languages as MonacoLanugauges,
  Range as MonacoRange,
  Position as MonacoPosition,
} from "monaco-editor";

...

private setDtsFiles(dtsFiles: DtsFile | DtsFile[]): void {
    if (Array.isArray(dtsFiles)) {
      const extraLibs = dtsFiles.map((x) => ({
        content: x.content,
        filePath: x.name,
      }));
      MonacoLanugauges.typescript.javascriptDefaults.setExtraLibs(extraLibs);
    } else {
      const tempDtsFiles = dtsFiles;
      const extraLibs = [
        { content: tempDtsFiles.content, filePath: tempDtsFiles.name },
      ];
      MonacoLanugauges.typescript.javascriptDefaults.setExtraLibs(extraLibs);
    }
  }

With the 15.0.3 version when we called this method, the new dts-files were applied succesfully and the libs could be use directly. But starting from the version 16.1.0 (we couldn't use the previous 16.x.x due to broken UI) when we call setDtsFiles the libs are only available after a reinitializing of the editor (our editor runs in an iframe and when we navigate away from the editor and back to it the new libs are available since they are being held in the overlaying C# code).

Can anybody help me and tell me what the cause of this new behavior could be? And maybe someone has a suggestion how to fix this?

Thank you very much for your help.

[Nuthin2do]

Here is a small very plain repro code ->

NewEditor_20250527.zip

With the v15.0.3 package as soon as i execute the setDtsFiles function, the code completion provides me "G.Test1". With v16.1.0 the code completion doesnt provide the "G.Test1".

Hope this helps to understand what i mean.

What is the cause of this different behavior?

Thanks in advance.

[CGNonofr]

Thanks for the report, it was indeed broken in the last version.

Microsoft did refactor quite a lot how worker works, but without actually updating monaco-editor and its workers, so I had to "hack" it to make it backward compatible, and there was an issue in that compatibility layer

fixed in #626