Files
vscode/build/monaco/monaco.usage.recipe
Matt Bierner 1eee7ae230 Switch monaco to off of moduleResolution: classic
Fixes #270408

Trying to move some of the monaco related checks/tconfigs off of `moduleResolution: classic`. This legacy config is causing a lot of pain while trying to update the trusted-types typings, which is itself blocking picking up the latest dompurify

I initially tried a more scoped change but just could not get it working. So instead I ended up trying to rework our `LanguageServiceHost` to be more standard
2025-10-10 16:02:03 -07:00

39 lines
1.0 KiB
Plaintext

// This file is adding references to various symbols which should not be removed via tree shaking
import { IObservable } from './vs/base/common/observable.js';
import { ServiceIdentifier } from './vs/platform/instantiation/common/instantiation.js';
import { start } from './vs/editor/editor.worker.start.js';
import { SyncDescriptor0 } from './vs/platform/instantiation/common/descriptors.js';
import * as editorAPI from './vs/editor/editor.api.js';
(function () {
var a: any;
var b: any;
a = (<ServiceIdentifier<any>>b).type;
a = start;
// injection madness
a = (<SyncDescriptor0<any>>b).ctor;
// exported API
a = editorAPI.CancellationTokenSource;
a = editorAPI.Emitter;
a = editorAPI.KeyCode;
a = editorAPI.KeyMod;
a = editorAPI.Position;
a = editorAPI.Range;
a = editorAPI.Selection;
a = editorAPI.SelectionDirection;
a = editorAPI.MarkerSeverity;
a = editorAPI.MarkerTag;
a = editorAPI.Uri;
a = editorAPI.Token;
a = editorAPI.editor;
a = editorAPI.languages;
const o: IObservable<number> = null!;
o.TChange;
})();