Skip to content

Bump the frontend-minor-patch group across 1 directory with 26 updates - #429

Open
dependabot[bot] wants to merge 1 commit into
devfrom
dependabot/npm_and_yarn/dev/frontend-minor-patch-d85cd2ab83
Open

Bump the frontend-minor-patch group across 1 directory with 26 updates#429
dependabot[bot] wants to merge 1 commit into
devfrom
dependabot/npm_and_yarn/dev/frontend-minor-patch-d85cd2ab83

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 19, 2026

Copy link
Copy Markdown
Contributor

Bumps the frontend-minor-patch group with 26 updates in the / directory:

Package From To
@azure/msal-browser 5.6.3 5.18.0
@codemirror/lang-markdown 6.5.1 6.5.2
@mui/x-tree-view 9.1.0 9.11.0
@tiptap/core 3.29.2 3.30.0
@tiptap/extension-image 3.29.2 3.30.0
@tiptap/extension-table 3.29.2 3.30.0
@tiptap/extension-table-cell 3.29.2 3.30.0
@tiptap/extension-table-header 3.29.2 3.30.0
@tiptap/extension-table-row 3.29.2 3.30.0
@tiptap/pm 3.29.2 3.30.0
@tiptap/react 3.29.2 3.30.0
@tiptap/starter-kit 3.29.2 3.30.0
canvas 3.2.2 3.2.3
i18next 26.0.1 26.3.6
katex 0.16.42 0.18.4
react-animate-height 3.2.3 3.2.4
react-arborist 3.7.0 3.16.0
react-virtuoso 4.18.3 4.18.11
validator 13.15.26 13.15.35
vega 6.2.0 6.4.0
vega-lite 6.4.1 6.4.3
@types/lodash 4.17.24 4.17.25
@typescript-eslint/eslint-plugin 8.65.0 8.67.0
@typescript-eslint/parser 8.65.0 8.67.0
typescript-eslint 8.65.0 8.67.0
vitest 4.1.1 4.1.10

Updates @azure/msal-browser from 5.6.3 to 5.18.0

Release notes

Sourced from @​azure/msal-browser's releases.

@​azure/msal-browser v5.18.0

5.18.0

Tue, 04 Aug 2026 20:17:38 GMT

Minor changes

Patches

  • Add internal webBrokerBridge scaffold (shared message interfaces, error taxonomy, pending-request registry) — no callers yet, no public API surface change #8729 (shylasummers@microsoft.com)

@​azure/msal-browser v5.17.3

5.17.3

Wed, 29 Jul 2026 00:26:30 GMT

Patches

  • Add single retry with 100ms backoff for token POST transport failures #8732 (thomas.norling@microsoft.com)
  • Streamline the platform broker request to only include the MSAL JS acquire-token parameters defined in the platform broker contract and params required on the ESTS /token call #8714 (lalima.sharda@gmail.com)
  • Fill telemetry gaps in platform brokering flow with extension #8699 (lalima.sharda@gmail.com)
  • Bump @​azure/msal-common to v16.11.3 (beachball)

@​azure/msal-browser v5.17.1

5.17.1

Wed, 15 Jul 2026 22:35:35 GMT

Patches

  • Add internal ES256/P-256 DPoP crypto support to BrowserCrypto #8683 (hectormmg@microsoft.com)
  • Bump @​azure/msal-common to v16.11.2 (beachball)

@​azure/msal-browser v5.17.0

5.17.0

Tue, 07 Jul 2026 22:16:01 GMT

Minor changes

  • Add auth.popupRelayUri: a double-popup option for apps that customize COOP/storage-partitioning, relaying acquireTokenPopup/logoutPopup through a top-level same-origin relay page (runPopupRelay) so tokens can be acquired from an untrusted cross-origin iframe. #8687 (kshabelko@microsoft.com)
  • Bump @​azure/msal-common to v16.11.1 (beachball)

Patches

... (truncated)

Commits
  • 5c53ac6 feat: add AttributeToken request and cache partition support (#8700)
  • 7d10e6c  [NAA/PWB One Bridge] PR 1/6: webBrokerBridge scaffold — shared interfaces, e...
  • 529fdd3 fix(msal-node): use length-prefix encoding for additional cache key hash to p...
  • 006de72 Add clientClaims request parameter for confidential client (#8686)
  • 2796e9b Bump uuid from 8.3.2 to 14.0.0 (#8575)
  • 45ac206 Bump immutable from 5.1.7 to 5.1.9 (#8718)
  • 8c1ec2d Bump webpack-dev-server from 5.2.3 to 5.2.6 (#8716)
  • cd19b1a Bump postcss from 8.5.15 to 8.5.18 (#8730)
  • 86bd093 test(e2e): shared brokering e2e helpers + real KMSI assertion (Foundation PR ...
  • a6a32af Post-release PR (#8734)
  • Additional commits viewable in compare view

Updates @codemirror/lang-markdown from 6.5.1 to 6.5.2

Commits

Updates @mui/x-tree-view from 9.1.0 to 9.11.0

Release notes

Sourced from @​mui/x-tree-view's releases.

v9.11.0

We'd like to extend a big thank you to the 14 contributors who made this release possible. Here are some highlights ✨:

  • ✨ Add addItems() and getItemSelection() API methods to Tree View

Special thanks go out to these community members for their valuable contributions: @​12joan, @​Anexus5919, @​kevincorizi-sbt, @​mixelburg, @​mustafajw07, @​strazto

The following team members contributed to this release: @​flaviendelangle, @​hasdfa, @​JCQuintas, @​LukasTy, @​MBilalShafi, @​michelengelen, @​noraleonte, @​rita-codes

Data Grid

@mui/x-data-grid@9.11.0

  • [DataGrid] Fix updateRows stripping class prototypes from rows in datasource mode (#22288) @​mixelburg
  • [DataGrid] Do not re-fetch data when an Activity becomes visible (#22603) @​12joan
  • [DataGrid] Fix toolbar button stealing focus when a sibling's disabled state changes (#23204) @​MBilalShafi

@mui/x-data-grid-pro@9.11.0 pro

Same changes as in @mui/x-data-grid@9.11.0.

@mui/x-data-grid-premium@9.11.0 premium

Same changes as in @mui/x-data-grid-pro@9.11.0.

Date and Time Pickers

@mui/x-date-pickers@9.11.0

  • [pickers] Fix day shift when editing dates predating timezone standardization (#23296) @​JCQuintas

@mui/x-date-pickers-pro@9.11.0 pro

Same changes as in @mui/x-date-pickers@9.11.0, plus:

  • [DateRangePicker] Fix disabled filler cells showing the range highlight (#23293) @​JCQuintas

Charts

@mui/x-charts@9.11.0

... (truncated)

Changelog

Sourced from @​mui/x-tree-view's changelog.

9.11.0

Aug 6, 2026

We'd like to extend a big thank you to the 14 contributors who made this release possible. Here are some highlights ✨:

  • ✨ Add addItems() and getItemSelection() API methods to Tree View

Special thanks go out to these community members for their valuable contributions: @​12joan, @​Anexus5919, @​kevincorizi-sbt, @​mixelburg, @​mustafajw07, @​strazto

The following team members contributed to this release: @​flaviendelangle, @​hasdfa, @​JCQuintas, @​LukasTy, @​MBilalShafi, @​michelengelen, @​noraleonte, @​rita-codes

Data Grid

@mui/x-data-grid@9.11.0

  • [DataGrid] Fix updateRows stripping class prototypes from rows in datasource mode (#22288) @​mixelburg
  • [DataGrid] Do not re-fetch data when an Activity becomes visible (#22603) @​12joan
  • [DataGrid] Fix toolbar button stealing focus when a sibling's disabled state changes (#23204) @​MBilalShafi

@mui/x-data-grid-pro@9.11.0 pro

Same changes as in @mui/x-data-grid@9.11.0.

@mui/x-data-grid-premium@9.11.0 premium

Same changes as in @mui/x-data-grid-pro@9.11.0.

Date and Time Pickers

@mui/x-date-pickers@9.11.0

  • [pickers] Fix day shift when editing dates predating timezone standardization (#23296) @​JCQuintas

@mui/x-date-pickers-pro@9.11.0 pro

Same changes as in @mui/x-date-pickers@9.11.0, plus:

  • [DateRangePicker] Fix disabled filler cells showing the range highlight (#23293) @​JCQuintas

Charts

@mui/x-charts@9.11.0

... (truncated)

Commits

Updates @tiptap/core from 3.29.2 to 3.30.0

Release notes

Sourced from @​tiptap/core's releases.

v3.30.0

@​tiptap/vue-2

Minor Changes

  • ceb0dac: New Decorations API

    Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

    Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

    Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

    addDecorations() {
  return {
    create: ({ state }) =>
      // findMatches can be any function that returns an array of { from, to } ranges
      findMatches(state.doc).map(match =>
        Decoration.Inline(match.from, match.to, { class: 'highlight' }),
      ),
  }
}

    There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

    Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

    Doing less work on every keystroke

    By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

    shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

    update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

    For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

    React and Vue components as widgets

    ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

    Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

    Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

    Documentation

... (truncated)

Changelog

Sourced from @​tiptap/core's changelog.

3.30.0

Minor Changes

  • 0247d39: ListKeymap now registers a Tab shortcut that sinks a top-level textblock into the previous list's last item. Pressing Tab at the start of a paragraph right after a bullet/ordered/task list moves the paragraph inside the last list item. The handler does nothing when the cursor is already inside a list item (sinkListItem keeps working), when there is no list before the paragraph, when the caret is mid-textblock, or when the selection is not a text selection (for example a gap cursor).

    @tiptap/core also exposes a new getPreviousBlockSibling($pos) helper that returns the block-level sibling before the cursor's textblock, or null at the first child of the block parent.

  • 3099eef: New Decorations API

    Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

    Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

    Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

    addDecorations() {
  return {
    create: ({ state }) =>
      // findMatches can be any function that returns an array of { from, to } ranges
      findMatches(state.doc).map(match =>
        Decoration.Inline(match.from, match.to, { class: 'highlight' }),
      ),
  }
}

    There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

    Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

    Doing less work on every keystroke

    By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

    shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

    update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

    For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

    React and Vue components as widgets

    ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

    Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

    Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

... (truncated)

Commits
  • 7901bc2 chore(release): release new stable release (#8142)
  • 3099eef feat(core): add Decorations API with framework widget renderers (#7902)
  • 51909d3 fix(core): insert content when prosemirror-model is loaded more than once (#8...
  • 0247d39 feat(extension-list-keymap): sink paragraph into previous list item on tab (#...
  • See full diff in compare view

Updates @tiptap/extension-image from 3.29.2 to 3.30.0

Release notes

Sourced from @​tiptap/extension-image's releases.

v3.30.0

@​tiptap/vue-2

Minor Changes

  • ceb0dac: New Decorations API

    Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

    Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

    Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

    addDecorations() {
  return {
    create: ({ state }) =>
      // findMatches can be any function that returns an array of { from, to } ranges
      findMatches(state.doc).map(match =>
        Decoration.Inline(match.from, match.to, { class: 'highlight' }),
      ),
  }
}

    There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

    Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

    Doing less work on every keystroke

    By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

    shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

    update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

    For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

    React and Vue components as widgets

    ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

    Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

    Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

    Documentation

... (truncated)

Changelog

Sourced from @​tiptap/extension-image's changelog.

3.30.0

Patch Changes

  • Updated dependencies [0247d39]
  • Updated dependencies [51909d3]
  • Updated dependencies [3099eef]
    • @​tiptap/core@​3.30.0
Commits

Updates @tiptap/extension-table from 3.29.2 to 3.30.0

Release notes

Sourced from @​tiptap/extension-table's releases.

v3.30.0

@​tiptap/vue-2

Minor Changes

  • ceb0dac: New Decorations API

    Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

    Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

    Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

    addDecorations() {
  return {
    create: ({ state }) =>
      // findMatches can be any function that returns an array of { from, to } ranges
      findMatches(state.doc).map(match =>
        Decoration.Inline(match.from, match.to, { class: 'highlight' }),
      ),
  }
}

    There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

    Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

    Doing less work on every keystroke

    By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

    shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

    update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

    For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

    React and Vue components as widgets

    ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

    Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

    Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

    Documentation

... (truncated)

Changelog

Sourced from @​tiptap/extension-table's changelog.

3.30.0

Patch Changes

  • eded5e4: Deleting the last row or column of a table no longer moves the cursor outside the table when there is content below it.
  • Updated dependencies [0247d39]
  • Updated dependencies [58a8953]
  • Updated dependencies [51909d3]
  • Updated dependencies [3099eef]
    • @​tiptap/core@​3.30.0
    • @​tiptap/pm@​3.30.0
Commits
  • 7901bc2 chore(release): release new stable release (#8142)
  • eded5e4 fix(extension-table): keep cursor inside table when deleting last row or colu...
  • See full diff in compare view

Updates @tiptap/extension-table-cell from 3.29.2 to 3.30.0

Release notes

Sourced from @​tiptap/extension-table-cell's releases.

v3.30.0

@​tiptap/vue-2

Minor Changes

  • ceb0dac: New Decorations API

    Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

    Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

    Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

    addDecorations() {
  return {
    create: ({ state }) =>
      // findMatches can be any function that returns an array of { from, to } ranges
      findMatches(state.doc).map(match =>
        Decoration.Inline(match.from, match.to, { class: 'highlight' }),
      ),
  }
}

    There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

    Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

    Doing less work on every keystroke

    By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

    shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

    update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

    For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

    React and Vue components as widgets

    ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

    Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

    Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

    Documentation

... (truncated)

Commits

Updates @tiptap/extension-table-header from 3.29.2 to 3.30.0

Release notes

Sourced from @​tiptap/extension-table-header's releases.

v3.30.0

@​tiptap/vue-2

Minor Changes

  • ceb0dac: New Decorations API

    Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

    Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

    Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

    addDecorations() {
  return {
    create: ({ state }) =>
      // findMatches can be any function that returns an array of { from, to } ranges
      findMatches(state.doc).map(match =>
        Decoration.Inline(match.from, match.to, { class: 'highlight' }),
      ),
  }
}

    There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

    Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

    Doing less work on every keystroke

    By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

    shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

    update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

    For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

    React and Vue components as widgets

    ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

    Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

    Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

    Documentation

... (truncated)

Commits

Updates @tiptap/extension-table-row from 3.29.2 to 3.30.0

Release notes

Sourced from @​tiptap/extension-table-row's releases.

v3.30.0

@​tiptap/vue-2

Minor Changes

  • ceb0dac: New Decorations API

    Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

    Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

    Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

    addDecorations() {
  return {
    create: ({ state }) =>
      // findMatches can be any function that returns an array of { from, to } ranges
      findMatches(state.doc).map(match =>
        Decoration.Inline(match.from, match.to, { class: 'highlight' }),
      ),
  }
}

    There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

    Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

    Doing less work on every keystroke

    By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

    shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

    update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

    For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

    React and Vue components as widgets

    ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

    Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

    Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

    Documentation

... (truncated)

Commits

Updates @tiptap/pm from 3.29.2 to 3.30.0

Release notes

Sourced from @​tiptap/pm's releases.

v3.30.0

@​tiptap/vue-2

Minor Changes

  • ceb0dac: New Decorations API

    Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

    Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

    Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

    addDecorations() {
  return {
    create: ({ state }) =>
      // findMatches can be any function that returns an array of { from, to } ranges
      findMatches(state.doc).map(match =>
        Decoration.Inline(match.from, match.to, { class: 'highlight' }),
      ),
  }
}

    There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

    Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

    Doing less work on every keystroke

    By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

    shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

    update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

    For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

    React and Vue components as widgets

    ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

    Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

    Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

    Documentation

... (truncated)

Changelog

Sourced from @​tiptap/pm's changelog.

3.30.0

Patch Changes

  • 58a8953: Fix the ./schema-list export map pointing types at dist/schema/, which is not emitted. Tools that read the types condition directly could not resolve @tiptap/pm/schema-list.
Commits

Updates @tiptap/react from 3.29.2 to 3.30.0

Release notes

Sourced from @​tiptap/react's releases.

v3.30.0

@​tiptap/vue-2

Minor Changes

  • ceb0dac: New Decorations API

    Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

    Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

    Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

    addDecorations() {
  return {
    create: ({ state }) =>
      // findMatches can be any function that returns an array of { from, to } ranges
      findMatches(state.doc).map(match =>
        Decoration.Inline(match.from, match.to, { class: 'highlight' }),
      ),
  }
}

    There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

    Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

    Doing less work on every keystroke

    By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

    shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

    update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

    For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

    React and Vue components as widgets

    ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

    Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

    Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

    Documentation

... (truncated)

Changelog

Sourced from @​tiptap/react's changelog.

3.30.0

Minor Changes

  • 3099eef: New Decorations API

    Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

    Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

    Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

    addDecorations() {
  return {
    create: ({ state }) =>
      // findMatches can be any function that returns an array of { from, to } ranges
      findMatches(state.doc).map(match =>
        Decoration.Inline(match.from, match.to, { class: 'highlight' }),
      ),
  }
}

    There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

    Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

    Doing less work on every keystroke

    By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

    shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

    update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

    For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

    React and Vue components as widgets

    ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

    Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

    Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

    Documentation

... (truncated)

Commits
  • 7901bc2 chore(release): release new stable release (#8142)
  • 3099eef feat(core): add Decorations API with framework widget renderers (#7902)
  • 31e176c fix(react): avoid stale position when syncing node view selection (

@dependabot
Bump the frontend-minor-patch group across 1 directory with 26 updates
d58675e 
Bumps the frontend-minor-patch group with 26 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@azure/msal-browser](https://github.com/AzureAD/microsoft-authentication-library-for-js) | `5.6.3` | `5.18.0` |
| [@codemirror/lang-markdown](https://github.com/codemirror/lang-markdown) | `6.5.1` | `6.5.2` |
| [@mui/x-tree-view](https://github.com/mui/mui-x/tree/HEAD/packages/x-tree-view) | `9.1.0` | `9.11.0` |
| [@tiptap/core](https://github.com/ueberdosis/tiptap/tree/HEAD/packages/core) | `3.29.2` | `3.30.0` |
| [@tiptap/extension-image](https://github.com/ueberdosis/tiptap/tree/HEAD/packages/extension-image) | `3.29.2` | `3.30.0` |
| [@tiptap/extension-table](https://github.com/ueberdosis/tiptap/tree/HEAD/packages/extension-table) | `3.29.2` | `3.30.0` |
| [@tiptap/extension-table-cell](https://github.com/ueberdosis/tiptap/tree/HEAD/packages/extension-table-cell) | `3.29.2` | `3.30.0` |
| [@tiptap/extension-table-header](https://github.com/ueberdosis/tiptap/tree/HEAD/packages/extension-table-header) | `3.29.2` | `3.30.0` |
| [@tiptap/extension-table-row](https://github.com/ueberdosis/tiptap/tree/HEAD/packages/extension-table-row) | `3.29.2` | `3.30.0` |
| [@tiptap/pm](https://github.com/ueberdosis/tiptap/tree/HEAD/packages/pm) | `3.29.2` | `3.30.0` |
| [@tiptap/react](https://github.com/ueberdosis/tiptap/tree/HEAD/packages/react) | `3.29.2` | `3.30.0` |
| [@tiptap/starter-kit](https://github.com/ueberdosis/tiptap/tree/HEAD/packages/starter-kit) | `3.29.2` | `3.30.0` |
| [canvas](https://github.com/Automattic/node-canvas) | `3.2.2` | `3.2.3` |
| [i18next](https://github.com/i18next/i18next) | `26.0.1` | `26.3.6` |
| [katex](https://github.com/KaTeX/KaTeX) | `0.16.42` | `0.18.4` |
| [react-animate-height](https://github.com/Stanko/react-animate-height) | `3.2.3` | `3.2.4` |
| [react-arborist](https://github.com/jameskerr/react-arborist) | `3.7.0` | `3.16.0` |
| [react-virtuoso](https://github.com/petyosi/react-virtuoso/tree/HEAD/packages/react-virtuoso) | `4.18.3` | `4.18.11` |
| [validator](https://github.com/validatorjs/validator.js) | `13.15.26` | `13.15.35` |
| [vega](https://github.com/vega/vega) | `6.2.0` | `6.4.0` |
| [vega-lite](https://github.com/vega/vega-lite) | `6.4.1` | `6.4.3` |
| [@types/lodash](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/lodash) | `4.17.24` | `4.17.25` |
| [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) | `8.65.0` | `8.67.0` |
| [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser) | `8.65.0` | `8.67.0` |
| [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint) | `8.65.0` | `8.67.0` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `4.1.1` | `4.1.10` |



Updates `@azure/msal-browser` from 5.6.3 to 5.18.0
- [Release notes](https://github.com/AzureAD/microsoft-authentication-library-for-js/releases)
- [Commits](AzureAD/microsoft-authentication-library-for-js@msal-browser-v5.6.3...msal-browser-v5.18.0)

Updates `@codemirror/lang-markdown` from 6.5.1 to 6.5.2
- [Changelog](https://github.com/codemirror/lang-markdown/blob/main/CHANGELOG.md)
- [Commits](https://github.com/codemirror/lang-markdown/commits)

Updates `@mui/x-tree-view` from 9.1.0 to 9.11.0
- [Release notes](https://github.com/mui/mui-x/releases)
- [Changelog](https://github.com/mui/mui-x/blob/master/CHANGELOG.md)
- [Commits](https://github.com/mui/mui-x/commits/v9.11.0/packages/x-tree-view)

Updates `@tiptap/core` from 3.29.2 to 3.30.0
- [Release notes](https://github.com/ueberdosis/tiptap/releases)
- [Changelog](https://github.com/ueberdosis/tiptap/blob/main/packages/core/CHANGELOG.md)
- [Commits](https://github.com/ueberdosis/tiptap/commits/v3.30.0/packages/core)

Updates `@tiptap/extension-image` from 3.29.2 to 3.30.0
- [Release notes](https://github.com/ueberdosis/tiptap/releases)
- [Changelog](https://github.com/ueberdosis/tiptap/blob/main/packages/extension-image/CHANGELOG.md)
- [Commits](https://github.com/ueberdosis/tiptap/commits/v3.30.0/packages/extension-image)

Updates `@tiptap/extension-table` from 3.29.2 to 3.30.0
- [Release notes](https://github.com/ueberdosis/tiptap/releases)
- [Changelog](https://github.com/ueberdosis/tiptap/blob/main/packages/extension-table/CHANGELOG.md)
- [Commits](https://github.com/ueberdosis/tiptap/commits/v3.30.0/packages/extension-table)

Updates `@tiptap/extension-table-cell` from 3.29.2 to 3.30.0
- [Release notes](https://github.com/ueberdosis/tiptap/releases)
- [Commits](https://github.com/ueberdosis/tiptap/commits/v3.30.0/packages/extension-table-cell)

Updates `@tiptap/extension-table-header` from 3.29.2 to 3.30.0
- [Release notes](https://github.com/ueberdosis/tiptap/releases)
- [Commits](https://github.com/ueberdosis/tiptap/commits/v3.30.0/packages/extension-table-header)

Updates `@tiptap/extension-table-row` from 3.29.2 to 3.30.0
- [Release notes](https://github.com/ueberdosis/tiptap/releases)
- [Commits](https://github.com/ueberdosis/tiptap/commits/v3.30.0/packages/extension-table-row)

Updates `@tiptap/pm` from 3.29.2 to 3.30.0
- [Release notes](https://github.com/ueberdosis/tiptap/releases)
- [Changelog](https://github.com/ueberdosis/tiptap/blob/main/packages/pm/CHANGELOG.md)
- [Commits](https://github.com/ueberdosis/tiptap/commits/v3.30.0/packages/pm)

Updates `@tiptap/react` from 3.29.2 to 3.30.0
- [Release notes](https://github.com/ueberdosis/tiptap/releases)
- [Changelog](https://github.com/ueberdosis/tiptap/blob/main/packages/react/CHANGELOG.md)
- [Commits](https://github.com/ueberdosis/tiptap/commits/v3.30.0/packages/react)

Updates `@tiptap/starter-kit` from 3.29.2 to 3.30.0
- [Release notes](https://github.com/ueberdosis/tiptap/releases)
- [Changelog](https://github.com/ueberdosis/tiptap/blob/main/packages/starter-kit/CHANGELOG.md)
- [Commits](https://github.com/ueberdosis/tiptap/commits/v3.30.0/packages/starter-kit)

Updates `canvas` from 3.2.2 to 3.2.3
- [Release notes](https://github.com/Automattic/node-canvas/releases)
- [Changelog](https://github.com/Automattic/node-canvas/blob/master/CHANGELOG.md)
- [Commits](Automattic/node-canvas@v3.2.2...v3.2.3)

Updates `i18next` from 26.0.1 to 26.3.6
- [Release notes](https://github.com/i18next/i18next/releases)
- [Changelog](https://github.com/i18next/i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/i18next@v26.0.1...v26.3.6)

Updates `katex` from 0.16.42 to 0.18.4
- [Release notes](https://github.com/KaTeX/KaTeX/releases)
- [Changelog](https://github.com/KaTeX/KaTeX/blob/main/CHANGELOG.md)
- [Commits](KaTeX/KaTeX@v0.16.42...v0.18.4)

Updates `react-animate-height` from 3.2.3 to 3.2.4
- [Changelog](https://github.com/Stanko/react-animate-height/blob/v3/CHANGELOG.md)
- [Commits](https://github.com/Stanko/react-animate-height/commits)

Updates `react-arborist` from 3.7.0 to 3.16.0
- [Release notes](https://github.com/jameskerr/react-arborist/releases)
- [Changelog](https://github.com/jameskerr/react-arborist/blob/main/CHANGELOG.md)
- [Commits](jameskerr/react-arborist@v3.7.0...v3.16.0)

Updates `react-virtuoso` from 4.18.3 to 4.18.11
- [Release notes](https://github.com/petyosi/react-virtuoso/releases)
- [Changelog](https://github.com/petyosi/react-virtuoso/blob/main/packages/react-virtuoso/CHANGELOG.md)
- [Commits](https://github.com/petyosi/react-virtuoso/commits/HEAD/packages/react-virtuoso)

Updates `validator` from 13.15.26 to 13.15.35
- [Release notes](https://github.com/validatorjs/validator.js/releases)
- [Changelog](https://github.com/validatorjs/validator.js/blob/master/CHANGELOG.md)
- [Commits](validatorjs/validator.js@13.15.26...13.15.35)

Updates `vega` from 6.2.0 to 6.4.0
- [Release notes](https://github.com/vega/vega/releases)
- [Commits](vega/vega@v6.2.0...v6.4.0)

Updates `vega-lite` from 6.4.1 to 6.4.3
- [Release notes](https://github.com/vega/vega-lite/releases)
- [Changelog](https://github.com/vega/vega-lite/blob/main/CHANGELOG.md)
- [Commits](vega/vega-lite@v6.4.1...v6.4.3)

Updates `@types/lodash` from 4.17.24 to 4.17.25
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/lodash)

Updates `@typescript-eslint/eslint-plugin` from 8.65.0 to 8.67.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.67.0/packages/eslint-plugin)

Updates `@typescript-eslint/parser` from 8.65.0 to 8.67.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.67.0/packages/parser)

Updates `typescript-eslint` from 8.65.0 to 8.67.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.67.0/packages/typescript-eslint)

Updates `vitest` from 4.1.1 to 4.1.10
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.10/packages/vitest)

---
updated-dependencies:
- dependency-name: "@azure/msal-browser"
  dependency-version: 5.18.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: "@codemirror/lang-markdown"
  dependency-version: 6.5.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: frontend-minor-patch
- dependency-name: "@mui/x-tree-view"
  dependency-version: 9.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: "@tiptap/core"
  dependency-version: 3.30.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: "@tiptap/extension-image"
  dependency-version: 3.30.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: "@tiptap/extension-table"
  dependency-version: 3.30.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: "@tiptap/extension-table-cell"
  dependency-version: 3.30.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: "@tiptap/extension-table-header"
  dependency-version: 3.30.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: "@tiptap/extension-table-row"
  dependency-version: 3.30.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: "@tiptap/pm"
  dependency-version: 3.30.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: "@tiptap/react"
  dependency-version: 3.30.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: "@tiptap/starter-kit"
  dependency-version: 3.30.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: canvas
  dependency-version: 3.2.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: frontend-minor-patch
- dependency-name: i18next
  dependency-version: 26.3.6
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: katex
  dependency-version: 0.18.4
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: react-animate-height
  dependency-version: 3.2.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: frontend-minor-patch
- dependency-name: react-arborist
  dependency-version: 3.16.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: react-virtuoso
  dependency-version: 4.18.11
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: frontend-minor-patch
- dependency-name: validator
  dependency-version: 13.15.35
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: frontend-minor-patch
- dependency-name: vega
  dependency-version: 6.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: vega-lite
  dependency-version: 6.4.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: frontend-minor-patch
- dependency-name: "@types/lodash"
  dependency-version: 4.17.25
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: frontend-minor-patch
- dependency-name: "@typescript-eslint/eslint-plugin"
  dependency-version: 8.67.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: "@typescript-eslint/parser"
  dependency-version: 8.67.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: typescript-eslint
  dependency-version: 8.67.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: frontend-minor-patch
- dependency-name: vitest
  dependency-version: 4.1.10
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: frontend-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Aug 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants