vscode/build/monaco
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
..
LICENSE
monaco.d.ts.recipe Switch monaco to off of moduleResolution: classic 2025-10-10 16:02:03 -07:00
monaco.usage.recipe Switch monaco to off of moduleResolution: classic 2025-10-10 16:02:03 -07:00
package.json Set monaco-editor-core version to 0.0.0 2021-12-10 15:30:43 +01:00
README-npm.md Fix supported markdown-lint violations in markdown files (#190750) 2023-08-24 08:37:25 +00:00
README.md
ThirdPartyNotices.txt
version.txt

Steps to publish a new version of monaco-editor-core

Generate monaco.d.ts

  • The monaco.d.ts is now automatically generated when running gulp watch

Bump version

  • increase version in build/monaco/package.json

Generate npm contents for monaco-editor-core

  • Be sure to have all changes committed and pushed to the remote
  • (the generated files contain the HEAD sha and that should be available on the remote)
  • run gulp editor-distro

Publish

  • cd out-monaco-editor-core
  • npm publish