fix: don't actually treat this like a typescript editor#1244
Merged
Conversation
lerouxb
commented
Feb 11, 2026
| monaco.typescript.typescriptDefaults.setCompilerOptions({ | ||
| target: monaco.typescript.ScriptTarget.Latest, | ||
| allowNonTsExtensions: true, | ||
| noLib: true, |
Contributor
Author
There was a problem hiding this comment.
This might be the only relevant line in this block 🤷
lerouxb
changed the title
lerouxb
added
the
no-title-validation
tculig
approved these changes
Feb 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After #1240 monaco is now loading all its code (most notably a web worker) and started to think that a document like
{ name }is referencing some deprecated DOM variable..This just turns off lots of things because this isn't actually a typescript editor.