fix(deps): update dependency @codemirror/language to ^6.11.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@codemirror/language	^6.6.0 -> ^6.11.0

---

Release Notes

codemirror/language (@​codemirror/language)

v6.11.0

Compare Source

New features

Stream parsers now support a mergeTokens option that can be used to turn off automatic merging of adjacent tokens.

v6.10.8

Compare Source

Bug fixes

Fix a regression introduced 6.10.7 that caused indention to sometimes crash on nested language boundaries.

v6.10.7

Compare Source

Bug fixes

Fix an issue where indentation for a stream language would fail to work when the parse covered only part of the document, far from the start.

Make sure the inner mode gets a chance to indent when indenting right at the end of a nested language section.

v6.10.6

Compare Source

Bug fixes

Fix a crash in StreamLanguage when the input range is entirely before the editor viewport.

v6.10.5

Compare Source

Bug fixes

Fix an issue where a StreamLanguage could get confused when trying to reuse existing parse data when the parsed range changed.

v6.10.4

Compare Source

Bug fixes

Join adjacent tokens of the same type into a single token in .

Call stream language indent functions even when the language is used as a nested parser.

Fix a crash in StreamParser when a parse was resumed with different input ranges.

v6.10.3

Compare Source

Bug fixes

Fix a TypeScript error when using HighlightStyle with the exactOptionalPropertyTypes typechecking option enabled.

Make delimitedIndent align to spaces after the opening token.

v6.10.2

Compare Source

Bug fixes

Fix an infinite loop that could occur when enabling bidiIsolates in documents with both bidirectional text and very long lines.

v6.10.1

Compare Source

Bug fixes

Fix an issue where, when a lot of code is visible in the initial editor, the bottom bit of code is shown without highlighting for one frame.

v6.10.0

Compare Source

New features

The new bidiIsolates extension can be used to wrap syntactic elements where this is appropriate in an element that isolates their text direction, avoiding weird ordering of neutral characters on direction boundaries.

v6.9.3

Compare Source

Bug fixes

Fix an issue in StreamLanguage where it ran out of node type ids if you repeatedly redefined a language with the same token table.

v6.9.2

Compare Source

Bug fixes

Allow StreamParser tokens get multiple highlighting tags.

v6.9.1

Compare Source

Bug fixes

Indentation now works a lot better in mixed-language documents that interleave the languages in a complex way.

Code folding is now able to pick the right foldable syntax node when the line end falls in a mixed-parsing language that doesn't match the target node.

v6.9.0

Compare Source

Bug fixes

Make getIndentation return null, rather than 0, when there is no syntax tree available.

New features

The new preparePlaceholder option to codeFolding makes it possible to display contextual information in a folded range placeholder widget.

v6.8.0

Compare Source

New features

The new baseIndentFor method in TreeIndentContext can be used to find the base indentation for an arbitrary node.

v6.7.0

Compare Source

New features

Export DocInput class for feeding editor documents to a Lezer parser.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	Mar 13, 2025 7:39pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 857ee97

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR