Type definitions for some classes

[Patrick Kranz (LokiMidgard)]

Maybe I overlooked it in the docs, but are there any typedefinitions for things like:

monaco-editor/esm/vs/editor/standalone/browser/standaloneServices.js
monaco-editor/esm/vs/editor/common/diff/rangeMapping.js
monaco-editor/esm/vs/editor/browser/widget/diffEditor/diffProviderFactoryService.js

I try to customize the dif algo, and noticed that typescript is not happy ;)

[Hosan (hosanxiv)]

You did not overlook a documented type package: those paths are internal deep modules, and the published package currently ships their .js files without matching .d.ts files.

Monaco's supported public editor surface is re-exported from monaco-editor-core/esm/vs/editor/editor.api (source), while the declaration build uses stripInternal: true (build config). That is why TypeScript is unhappy with imports such as standaloneServices.js, rangeMapping.js, and diffProviderFactoryService.js: they are implementation details rather than a typed extension API.

Practical options:

• If the public diff options are sufficient, import the API/types from monaco-editor and stay on the supported surface.
• If you must use those internals, add local ambient declarations for only the members you consume (for example in monaco-internals.d.ts). Keep them narrow and pin your Monaco version.
• Alternatively, derive declarations from the matching VS Code/Monaco source revision, but treat them as vendored compatibility code and re-check them on every upgrade.

I would not use a broad declare module "..." with implicit any; it suppresses the error but removes the protection you wanted from TypeScript. Also, a custom diff implementation through diffProviderFactoryService is inherently version-sensitive because that service is not part of Monaco's public API.

[Patrick Kranz (LokiMidgard)]

Thank you very much :)