chore(deps): bump the bun-dependencies group across 1 directory with 22 updates

[dependabot]

Bumps the bun-dependencies group with 22 updates in the / directory:

Package	From	To
@biomejs/biome	2.5.12	2.5.14
@lexical/html	0.50.0	0.51.0
@lexical/react	0.50.0	0.51.0
@sentry/react	10.73.0	10.75.0
@simplewebauthn/browser	13.3.0	14.0.0
@tanstack/react-query	5.102.8	5.103.1
@tanstack/react-virtual	3.14.10	3.14.13
lexical	0.50.0	0.51.0
lucide-react	1.41.0	1.47.0
react	19.2.8	19.3.0
@types/react	19.2.18	19.3.0
react-dom	19.2.8	19.3.0
@types/react-dom	19.2.7	19.3.0
react-router	8.3.1	8.4.0
tailwind-merge	3.6.0	3.7.0
@types/react	19.2.18	19.3.0
@types/react-dom	19.2.7	19.3.0
jsdom	30.0.1	30.1.0
vite	8.2.2	8.3.0
vitest	5.0.0	5.0.1
@better-auth/passkey	1.7.3	1.7.5
auth	1.7.3	1.7.5
better-auth	1.7.3	1.7.5
@types/bun	1.4.0	1.4.2

Updates @biomejs/biome from 2.5.12 to 2.5.14

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.5.14

2.5.14

Patch Changes

• #9022 0d49e24 Thanks @​dyc3! - Added the nursery rule noReturnInFinally. This rule disallows return statements in Promise.prototype.finally() callbacks, including inside nested blocks and conditional branches. Returns in nested functions are ignored by the rule.

  // Invalid: return in finally callback
  Promise.resolve(1).finally(() => { return 2 })
  // Valid: no return in finally callback
  Promise.resolve(1).finally(() => { console.log(2) })

  Returning a value from a Promise.prototype.finally() callback does not replace the original promise's fulfillment value, which can be confusing. Returned promises and thenables are awaited, and their rejection rejects the resulting promise.

• #11754 71eaa0d Thanks @​griff-rees! - Added the nursery rule noSvelteAtDebugTags, which disallows Svelte's {@debug} tag.

  <!-- Invalid: leftover debugging tag -->
  {@debug user}

  The {@debug} tag is a debugging aid and should be removed once you no longer need it, as it should not remain in production code. The rule provides a safe fix that removes the tag.

• #11725 5eb5f09 Thanks @​m1handr! - Added the nursery rule useValidTestTitle, which enforces valid titles for unit test cases and suites.

• #11735 9bd70c7 Thanks @​ematipico! - Fixed #8471: source.fixAll.biome ignored formatter.formatWithErrors. It now applies safe fixes without formatting files that have parse errors when the option is disabled.

• #11715 f05a3c3 Thanks @​ematipico! - Fixed #7771: Grit plugins that use sequential no longer panic when Biome processes files.

• #11766 c2542c6 Thanks @​dyc3! - Fixed validation of readonly and accessor modifiers: combining them in either order now reports that they cannot be used together.

• #11461 22e9966 Thanks @​FoundDream! - Fixed #11423: Multiline template interpolations now preserve the indentation of their closing brace when the source indentation is not a multiple of tabWidth.

   const value = `
        ${
          condition
            ? "yes"
            : "no"
  -}
  +     }
   `;

• #11766 c2542c6 Thanks @​dyc3! - Fixed #11763: TypeScript class members using override accessor, such as override accessor value = 1, now parse correctly. The reversed order, accessor override, now reports that override must precede accessor.

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.5.14

Patch Changes

• #9022 0d49e24 Thanks @​dyc3! - Added the nursery rule noReturnInFinally. This rule disallows return statements in Promise.prototype.finally() callbacks, including inside nested blocks and conditional branches. Returns in nested functions are ignored by the rule.

  // Invalid: return in finally callback
  Promise.resolve(1).finally(() => { return 2 })
  // Valid: no return in finally callback
  Promise.resolve(1).finally(() => { console.log(2) })

  Returning a value from a Promise.prototype.finally() callback does not replace the original promise's fulfillment value, which can be confusing. Returned promises and thenables are awaited, and their rejection rejects the resulting promise.

• #11754 71eaa0d Thanks @​griff-rees! - Added the nursery rule noSvelteAtDebugTags, which disallows Svelte's {@debug} tag.

  <!-- Invalid: leftover debugging tag -->
  {@debug user}

  The {@debug} tag is a debugging aid and should be removed once you no longer need it, as it should not remain in production code. The rule provides a safe fix that removes the tag.

• #11725 5eb5f09 Thanks @​m1handr! - Added the nursery rule useValidTestTitle, which enforces valid titles for unit test cases and suites.

• #11735 9bd70c7 Thanks @​ematipico! - Fixed #8471: source.fixAll.biome ignored formatter.formatWithErrors. It now applies safe fixes without formatting files that have parse errors when the option is disabled.

• #11715 f05a3c3 Thanks @​ematipico! - Fixed #7771: Grit plugins that use sequential no longer panic when Biome processes files.

• #11766 c2542c6 Thanks @​dyc3! - Fixed validation of readonly and accessor modifiers: combining them in either order now reports that they cannot be used together.

• #11461 22e9966 Thanks @​FoundDream! - Fixed #11423: Multiline template interpolations now preserve the indentation of their closing brace when the source indentation is not a multiple of tabWidth.

   const value = `
        ${
          condition
            ? "yes"
            : "no"
  -}
  +     }
   `;

• #11766 c2542c6 Thanks @​dyc3! - Fixed #11763: TypeScript class members using override accessor, such as override accessor value = 1, now parse correctly. The reversed order, accessor override, now reports that override must precede accessor.

• #11790 17d0ff0 Thanks @​ematipico! - Fixed #10248: noUselessFragments now allows fragments with props in Astro files, such as <Fragment slot="name">{text}</Fragment> inside template expressions.

... (truncated)

Commits

• af4365d ci: release (#11711)
• 7ee3a6c fix(useExhaustiveSwitchCases): add option requireExplicitCase (#11777)
• 02ea438 feat(json_analyze): implement noJsonUnsafeValues (#9758)
• 64fd314 feat(json_analyze): implement useConsistentObjectKeys (#9797)
• a9c4aa0 feat(html): detect undeclared custom Vue directives (#11651)
• 1fc17e3 feat: expand useIncludes (#11739)
• 71eaa0d feat(lint/html/svelte): add noSvelteAtDebugTags (#11754)
• 9bd70c7 fix: various bug fixes (#11735)
• c7c4e2b fix(analyzer): various bugs (#11720)
• 5eb5f09 feat(biome_js_analyze): implement useValidTestTitle rule (#9176) (#11725)
• Additional commits viewable in compare view

Updates @lexical/html from 0.50.0 to 0.51.0

Release notes

Sourced from @​lexical/html's releases.

v0.51.0 is a monthly release with one large new feature: nodes can now declare their JSON serialization as a schema on $config. This declarative schema is faster, safer, and more flexible than the hand-written methods. The metadata it provides enables a compact export option with all default values elided, the code generator that provides faster import and export for every node that lexical ships, a new @lexical/fast-check package for property-based tests, and it provides a path to future features that rely on knowing the structure of the nodes (e.g. additional codecs and dev tools).

This is a big step towards Lexical 1.0, the next few releases are expected to be focused on moving everything (including docs and examples) to the latest Extension and $config APIs and removing deprecated functionality. Two related changes in this release are that we are publishing ESM-only to npm now (cjs builds are still supported in the source tree), and LexicalComposer is deprecated for LexicalExtensionComposer. Expect anything @deprecated to be removed soon.

Breaking Changes

• npm packages are ESM only. Every package declares "type": "module" and its exports map offers development / production / default conditions with no require branch; the CommonJS build remains in-tree only for Meta's www. Bundlers are unaffected. CommonJS code can require() the packages on Node.js 20.19+ (the builds have no top-level await), and older Node.js must use await import(...) — but a dependency the app also loads through require() can then exist twice, which breaks handing its objects to Lexical (yjs docs to @lexical/yjs, @preact/signals-core signals from @lexical/extension), so load those as ESM too. Metro bundles both builds unless you add the condition for Lexical's packages; see the module formats FAQ (#9127)
• lexical — exportJSON may serialize the instance as-is. A property declared with withField is read straight off the node instead of through its accessor, so exportJSON no longer resolves getLatest() for you and a stale reference can write stale values (and a property whose accessor a subclass overrode still resolves, so one object can mix the two). Nothing inside Lexical is affected — the walk, the clipboard selection export and editorState.toJSON() all start from the node map — but call getLatest() yourself on a reference you kept across a mutation (#8602)
• @lexical/code — the deprecated Prism re-exports are gone, along with the @lexical/code-prism dependency (so Prism no longer lands in a bundle that only imports @lexical/code). Import CODE_LANGUAGE_FRIENDLY_NAME_MAP, CODE_LANGUAGE_MAP, getCodeLanguageOptions, getCodeLanguages, getCodeThemeOptions, getLanguageFriendlyName, normalizeCodeLanguage (formerly also normalizeCodeLang), PrismTokenizer and registerCodeHighlighting from @lexical/code-prism (#9141)

Deprecations

• @lexical/react — LexicalComposer is deprecated in favor of LexicalExtensionComposer and is expected to be removed in a future major. LexicalComposer cannot accept extensions, so any feature shipped as one is unreachable from an editor it builds; the migration is usually a two-line change (#9168, React extensions guide)

New APIs & Features

• lexical — Declarative serialization schemas (experimental). A node that uses $config declares its serialized properties once in the new json property, and that single declaration drives importJSON, updateFromJSON and exportJSON: nodeSchema, withField / withAccessors, and the value combinators (stringValue, numberValue, booleanValue, enumValue, arrayValue, objectValue, unionValue, rawValue, transformValue, nullable, optional, …). Every built-in node declares one, and most custom nodes now need no JSON serialization code at all. Output is unchanged by default (#8602, serialization docs).
• lexical — Compact JSON export, opt-in via editorState.toJSON(true) or $withCompactExport(true, cb) (with $isCompactExport() for schema getters, plus $exportNodeJSON and the CompactSerializedEditorState / ParsableSerializedEditorState / LexicalParseJSON / SerializedPartial types). It omits properties equal to their schema default, properties the parser derives, and the deprecated version. The raw objects are well under half the legacy size — which matters for structured clones and worker messages — but after gzip the two are a wash. Both forms parse back to the same document; only a Lexical new enough to know the schemas can read the compact one, so keep writing the legacy form until every reader is upgraded (#8602)
• @lexical/compiler — Generated serialization code. Every built-in node class ships straight-line serialization generated from its own schema at build time, producing byte-identical JSON to the schema-driven path that continues to serve custom nodes (#8602)
• @lexical/fast-check — New package deriving fast-check arbitraries from those schemas: nodeArbitrary(NodeClass) generates exactly the serialized JSON a node's parser accepts, each property independently present or absent. Useful for the bugs fixtures hide, such as a property afterCloneFrom forgot to copy. fast-check is a peer dependency; getComposedSchemaFields in core inspects a class's schema without generating anything (#8602)
• @lexical/extension — Published as subpath exports, one entry per extension (@lexical/extension/AutoFocusExtension, …), with compiler and lint enforcement of the source import convention. The barrel import is unchanged, and shared modules such as signals keep a single instance (#9161). This is primarily only useful as a consumer if you are not using tree-shaking.

Notable Fixes

Bundling, tree-shaking & types

• A production import of only createCommand no longer retains the editor (#9121), and the remaining module-scope side effects that defeated tree-shaking are gone, with a bare-import residue check now run over every entry (#9124); extension editors build under loose-mode transpilation (#9134)
• Flow: defineExtension was uncallable, making the extension types unusable (#9132); declarations can now express an extension with dependencies (#9176); modern variance keywords survive into the www stubs (#9154)

Selection & editing

• No redundant selection-change command on Safari link selection (#9163); TextNode.setMode, setTextContent and isSimpleText read the latest state (#9162); $removeTextFromCaretRange no longer leaves a childless list or table as the root's only child (#9116); a text entity keeps the style and detail of the text it replaces (#9130); selection overlay listeners are notified when rectangles are removed (#9117)

Lists, tables & Markdown

• Indenting between two nested lists no longer converts the second list's type (#9118); $mergeCells no longer keeps the empty paragraph of the target cell (#9122); text left outside a Markdown link keeps its format (#9131)

Playground & docs

• Card/Review CSS placeholders are cleared reliably on paste in Safari (#9129) and releasing a CardNode drag no longer selects the node (#9135); new docs on Lexical being a singleton per app, and why a library must declare it as a peer dependency (#9125)

Plus the usual dependency updates across the rollup, shikijs, vitest, docusaurus/typedoc and flow/hermes groups.

What's Changed

• v0.50.0 by @​etrepum in facebook/lexical#9110
• [lexical][lexical-compiler] Bug Fix: Let esbuild drop the editor from a createCommand-only production import by @​zurfyx in facebook/lexical#9121
• [*] Bug Fix: Remove the remaining module-scope side effects that defeat tree-shaking by @​etrepum in facebook/lexical#9124
• [lexical-playground] Bug Fix: clear Card/Review CSS placeholders reliably on paste in Safari by @​sahiee-dev in facebook/lexical#9129
• [lexical-website] Documentation Update: document that Lexical is a singleton per app and libraries must declare it as a peer dependency by @​potatowagon in facebook/lexical#9125
• [lexical-markdown] Bug Fix: text left outside a markdown link keeps its format by @​Om-singhaI in facebook/lexical#9131

... (truncated)

Changelog

Sourced from @​lexical/html's changelog.

v0.51.0 (2026-09-17)

• build(deps-dev) bump the vitest group across 1 directory with 2 updates (#9157) dependabotbot
• build(deps) bump immutable from 4.3.8 to 4.3.9 (#9175) dependabotbot
• build(deps) bump babelparser from 8.0.0 to 8.0.4 (#9160) dependabotbot
• lexical Feature node JSON serialization schemas, with compact export (#8602) Bob Ippolito
• build(deps) bump date-fns from 4.1.0 to 4.4.0 (#9159) dependabotbot
• build(deps-dev) bump eslint from 10.9.1 to 10.10.0 in the dev-dependencies group across 1 directory (#9158) dependabotbot
• lexical-react Chore Deprecate LexicalComposer in favor of LexicalExtensionComposer (#9168) Sherry
• lexical Bug Fix TextNode setMode, setTextContent and isSimpleText read the latest state (#9162) Leo Camus
• lexical Bug Fix Avoid redundant selection change command (#9163) Sergey Gorbachev
• lexical-extension Refactor publish lexicalextension as subpath exports with compilerlint enforcement (#9161) Bob Ippolito
• build(deps-dev) bump flow-bin from 0.330.0 to 0.331.0 in the flow-and-hermes group (#9156) dependabotbot
• build(deps-dev) bump the dev-dependencies group across 1 directory with 26 updates (#9150) dependabotbot
• Bug Fix Keep modern Flow variance keywords in the www Flow stubs (#9154) Sherry
• lexical-list Bug Fix indenting between two nested lists no longer converts the second lists type (#9118) om singhal
• build(deps) bump the rollup group across 1 directory with 5 updates (#9144) dependabotbot
• build(deps) bump the shikijs group with 6 updates (#9145) dependabotbot
• build(deps-dev) bump baseline-browser-mapping from 2.10.33 to 2.11.0 (#9139) dependabotbot
• build(deps-dev) bump the flow-and-hermes group with 4 updates (#9143) dependabotbot
• build(deps) bump the docusaurus-and-typedoc group with 13 updates (#9142) dependabotbot
• build(deps-dev) bump vitest from 4.1.8 to 4.1.11 (#9140) dependabotbot
• lexical-code Breaking change drop the deprecated prism re-exports and the lexicalcode-prism dependency (#9141) Bob Ippolito
• Breaking change Publish ESM only to npm and keep the CommonJS build for www (#9127) Bob Ippolito
• lexical-text Bug Fix a text entity keeps the style and detail of the text it replaces (#9130) om singhal
• lexical-extension Fix use Array.from over iterable spread so extension editors build under loose-mode transpilation (#9134) Sherry
• lexical-playground Bug Fix avoid node selection on CardNode drag release (#9135) KAVYANSH KUMAR
• lexical Bug Fix removeTextFromCaretRange no longer leaves a childless list or table as the roots only child (#9116) om singhal
• lexical-utils Bug Fix notify when selection overlay rectangles are removed (#9117) Mehul Jariwala
• lexical-table Bug Fix mergeCells no longer keeps the empty paragraph of the target cell (#9122) om singhal
• build(deps-dev) bump esbuild from 0.27.7 to 0.28.1 (#9123) dependabotbot
• lexical Fix make the extension Flow types usable (defineExtension was uncallable) (#9132) Sherry
• lexical-markdown Bug Fix text left outside a markdown link keeps its format (#9131) om singhal
• lexical-website Documentation Update document that Lexical is a singleton per app and libraries must declare it as a peer dependency (#9125) Sherry
• lexical-playground Bug Fix clear CardReview CSS placeholders reliably on paste in Safari (#9129) sahir
• Bug Fix Remove the remaining module-scope side effects that defeat tree-shaking (#9124) Bob Ippolito
• lexicallexical-compiler Bug Fix Let esbuild drop the editor from a createCommand-only production import (#9121) Gerard Rovira
• v0.50.0 (#9110) Bob Ippolito
• v0.50.0 Lexical GitHub Actions Bot

Commits

• 4c61ded v0.51.0
• 737b3af [*] Breaking change: Publish ESM only to npm and keep the CommonJS build for ...
• 45f8aa4 [*] Bug Fix: Remove the remaining module-scope side effects that defeat tree-...
• c3b629d v0.50.0 (#9110)
• See full diff in compare view

Updates @lexical/react from 0.50.0 to 0.51.0

Release notes

Sourced from @​lexical/react's releases.

v0.51.0 is a monthly release with one large new feature: nodes can now declare their JSON serialization as a schema on $config. This declarative schema is faster, safer, and more flexible than the hand-written methods. The metadata it provides enables a compact export option with all default values elided, the code generator that provides faster import and export for every node that lexical ships, a new @lexical/fast-check package for property-based tests, and it provides a path to future features that rely on knowing the structure of the nodes (e.g. additional codecs and dev tools).

This is a big step towards Lexical 1.0, the next few releases are expected to be focused on moving everything (including docs and examples) to the latest Extension and $config APIs and removing deprecated functionality. Two related changes in this release are that we are publishing ESM-only to npm now (cjs builds are still supported in the source tree), and LexicalComposer is deprecated for LexicalExtensionComposer. Expect anything @deprecated to be removed soon.

Breaking Changes

• npm packages are ESM only. Every package declares "type": "module" and its exports map offers development / production / default conditions with no require branch; the CommonJS build remains in-tree only for Meta's www. Bundlers are unaffected. CommonJS code can require() the packages on Node.js 20.19+ (the builds have no top-level await), and older Node.js must use await import(...) — but a dependency the app also loads through require() can then exist twice, which breaks handing its objects to Lexical (yjs docs to @lexical/yjs, @preact/signals-core signals from @lexical/extension), so load those as ESM too. Metro bundles both builds unless you add the condition for Lexical's packages; see the module formats FAQ (#9127)
• lexical — exportJSON may serialize the instance as-is. A property declared with withField is read straight off the node instead of through its accessor, so exportJSON no longer resolves getLatest() for you and a stale reference can write stale values (and a property whose accessor a subclass overrode still resolves, so one object can mix the two). Nothing inside Lexical is affected — the walk, the clipboard selection export and editorState.toJSON() all start from the node map — but call getLatest() yourself on a reference you kept across a mutation (#8602)
• @lexical/code — the deprecated Prism re-exports are gone, along with the @lexical/code-prism dependency (so Prism no longer lands in a bundle that only imports @lexical/code). Import CODE_LANGUAGE_FRIENDLY_NAME_MAP, CODE_LANGUAGE_MAP, getCodeLanguageOptions, getCodeLanguages, getCodeThemeOptions, getLanguageFriendlyName, normalizeCodeLanguage (formerly also normalizeCodeLang), PrismTokenizer and registerCodeHighlighting from @lexical/code-prism (#9141)

Deprecations

• @lexical/react — LexicalComposer is deprecated in favor of LexicalExtensionComposer and is expected to be removed in a future major. LexicalComposer cannot accept extensions, so any feature shipped as one is unreachable from an editor it builds; the migration is usually a two-line change (#9168, React extensions guide)

New APIs & Features

• lexical — Declarative serialization schemas (experimental). A node that uses $config declares its serialized properties once in the new json property, and that single declaration drives importJSON, updateFromJSON and exportJSON: nodeSchema, withField / withAccessors, and the value combinators (stringValue, numberValue, booleanValue, enumValue, arrayValue, objectValue, unionValue, rawValue, transformValue, nullable, optional, …). Every built-in node declares one, and most custom nodes now need no JSON serialization code at all. Output is unchanged by default (#8602, serialization docs).
• lexical — Compact JSON export, opt-in via editorState.toJSON(true) or $withCompactExport(true, cb) (with $isCompactExport() for schema getters, plus $exportNodeJSON and the CompactSerializedEditorState / ParsableSerializedEditorState / LexicalParseJSON / SerializedPartial types). It omits properties equal to their schema default, properties the parser derives, and the deprecated version. The raw objects are well under half the legacy size — which matters for structured clones and worker messages — but after gzip the two are a wash. Both forms parse back to the same document; only a Lexical new enough to know the schemas can read the compact one, so keep writing the legacy form until every reader is upgraded (#8602)
• @lexical/compiler — Generated serialization code. Every built-in node class ships straight-line serialization generated from its own schema at build time, producing byte-identical JSON to the schema-driven path that continues to serve custom nodes (#8602)
• @lexical/fast-check — New package deriving fast-check arbitraries from those schemas: nodeArbitrary(NodeClass) generates exactly the serialized JSON a node's parser accepts, each property independently present or absent. Useful for the bugs fixtures hide, such as a property afterCloneFrom forgot to copy. fast-check is a peer dependency; getComposedSchemaFields in core inspects a class's schema without generating anything (#8602)
• @lexical/extension — Published as subpath exports, one entry per extension (@lexical/extension/AutoFocusExtension, …), with compiler and lint enforcement of the source import convention. The barrel import is unchanged, and shared modules such as signals keep a single instance (#9161). This is primarily only useful as a consumer if you are not using tree-shaking.

Notable Fixes

Bundling, tree-shaking & types

• A production import of only createCommand no longer retains the editor (#9121), and the remaining module-scope side effects that defeated tree-shaking are gone, with a bare-import residue check now run over every entry (#9124); extension editors build under loose-mode transpilation (#9134)
• Flow: defineExtension was uncallable, making the extension types unusable (#9132); declarations can now express an extension with dependencies (#9176); modern variance keywords survive into the www stubs (#9154)

Selection & editing

• No redundant selection-change command on Safari link selection (#9163); TextNode.setMode, setTextContent and isSimpleText read the latest state (#9162); $removeTextFromCaretRange no longer leaves a childless list or table as the root's only child (#9116); a text entity keeps the style and detail of the text it replaces (#9130); selection overlay listeners are notified when rectangles are removed (#9117)

Lists, tables & Markdown

• Indenting between two nested lists no longer converts the second list's type (#9118); $mergeCells no longer keeps the empty paragraph of the target cell (#9122); text left outside a Markdown link keeps its format (#9131)

Playground & docs

• Card/Review CSS placeholders are cleared reliably on paste in Safari (#9129) and releasing a CardNode drag no longer selects the node (#9135); new docs on Lexical being a singleton per app, and why a library must declare it as a peer dependency (#9125)

Plus the usual dependency updates across the rollup, shikijs, vitest, docusaurus/typedoc and flow/hermes groups.

What's Changed

• v0.50.0 by @​etrepum in facebook/lexical#9110
• [lexical][lexical-compiler] Bug Fix: Let esbuild drop the editor from a createCommand-only production import by @​zurfyx in facebook/lexical#9121
• [*] Bug Fix: Remove the remaining module-scope side effects that defeat tree-shaking by @​etrepum in facebook/lexical#9124
• [lexical-playground] Bug Fix: clear Card/Review CSS placeholders reliably on paste in Safari by @​sahiee-dev in facebook/lexical#9129
• [lexical-website] Documentation Update: document that Lexical is a singleton per app and libraries must declare it as a peer dependency by @​potatowagon in facebook/lexical#9125
• [lexical-markdown] Bug Fix: text left outside a markdown link keeps its format by @​Om-singhaI in facebook/lexical#9131

... (truncated)

Changelog

Sourced from @​lexical/react's changelog.

v0.51.0 (2026-09-17)

• build(deps-dev) bump the vitest group across 1 directory with 2 updates (#9157) dependabotbot
• build(deps) bump immutable from 4.3.8 to 4.3.9 (#9175) dependabotbot
• build(deps) bump babelparser from 8.0.0 to 8.0.4 (#9160) dependabotbot
• lexical Feature node JSON serialization schemas, with compact export (#8602) Bob Ippolito
• build(deps) bump date-fns from 4.1.0 to 4.4.0 (#9159) dependabotbot
• build(deps-dev) bump eslint from 10.9.1 to 10.10.0 in the dev-dependencies group across 1 directory (#9158) dependabotbot
• lexical-react Chore Deprecate LexicalComposer in favor of LexicalExtensionComposer (#9168) Sherry
• lexical Bug Fix TextNode setMode, setTextContent and isSimpleText read the latest state (#9162) Leo Camus
• lexical Bug Fix Avoid redundant selection change command (#9163) Sergey Gorbachev
• lexical-extension Refactor publish lexicalextension as subpath exports with compilerlint enforcement (#9161) Bob Ippolito
• build(deps-dev) bump flow-bin from 0.330.0 to 0.331.0 in the flow-and-hermes group (#9156) dependabotbot
• build(deps-dev) bump the dev-dependencies group across 1 directory with 26 updates (#9150) dependabotbot
• Bug Fix Keep modern Flow variance keywords in the www Flow stubs (#9154) Sherry
• lexical-list Bug Fix indenting between two nested lists no longer converts the second lists type (#9118) om singhal
• build(deps) bump the rollup group across 1 directory with 5 updates (#9144) dependabotbot
• build(deps) bump the shikijs group with 6 updates (#9145) dependabotbot
• build(deps-dev) bump baseline-browser-mapping from 2.10.33 to 2.11.0 (#9139) dependabotbot
• build(deps-dev) bump the flow-and-hermes group with 4 updates (#9143) dependabotbot
• build(deps) bump the docusaurus-and-typedoc group with 13 updates (#9142) dependabotbot
• build(deps-dev) bump vitest from 4.1.8 to 4.1.11 (#9140) dependabotbot
• lexical-code Breaking change drop the deprecated prism re-exports and the lexicalcode-prism dependency (#9141) Bob Ippolito
• Breaking change Publish ESM only to npm and keep the CommonJS build for www (#9127) Bob Ippolito
• lexical-text Bug Fix a text entity keeps the style and detail of the text it replaces (#9130) om singhal
• lexical-extension Fix use Array.from over iterable spread so extension editors build under loose-mode transpilation (#9134) Sherry
• lexical-playground Bug Fix avoid node selection on CardNode drag release (#9135) KAVYANSH KUMAR
• lexical Bug Fix removeTextFromCaretRange no longer leaves a childless list or table as the roots only child (#9116) om singhal
• lexical-utils Bug Fix notify when selection overlay rectangles are removed (#9117) Mehul Jariwala
• lexical-table Bug Fix mergeCells no longer keeps the empty paragraph of the target cell (#9122) om singhal
• build(deps-dev) bump esbuild from 0.27.7 to 0.28.1 (#9123) dependabotbot
• lexical Fix make the extension Flow types usable (defineExtension was uncallable) (#9132) Sherry
• lexical-markdown Bug Fix text left outside a markdown link keeps its format (#9131) om singhal
• lexical-website Documentation Update document that Lexical is a singleton per app and libraries must declare it as a peer dependency (#9125) Sherry
• lexical-playground Bug Fix clear CardReview CSS placeholders reliably on paste in Safari (#9129) sahir
• Bug Fix Remove the remaining module-scope side effects that defeat tree-shaking (#9124) Bob Ippolito
• lexicallexical-compiler Bug Fix Let esbuild drop the editor from a createCommand-only production import (#9121) Gerard Rovira
• v0.50.0 (#9110) Bob Ippolito
• v0.50.0 Lexical GitHub Actions Bot

Commits

• 4c61ded v0.51.0
• 90f4e5f [lexical] Fix: Flow declarations cannot express an extension with dependencie...
• 4973ca1 build(deps-dev): bump the vitest group across 1 directory with 2 updates (#9157)
• a02c61b [lexical][*] Feature: node JSON serialization schemas, with compact export (#...
• f73868b [lexical-react] Chore: Deprecate LexicalComposer in favor of LexicalExtension...
• ca0afc4 build(deps-dev): bump the dev-dependencies group across 1 directory with 26 u...
• 737b3af [*] Breaking change: Publish ESM only to npm and keep the CommonJS build for ...
• 45f8aa4 [*] Bug Fix: Remove the remaining module-scope side effects that defeat tree-...
• c3b629d v0.50.0 (#9110)
• See full diff in compare view

Updates @sentry/react from 10.73.0 to 10.75.0

Release notes

Sourced from @​sentry/react's releases.

10.75.0

Important Changes

• feat(v10/effect): Capture errors through the Effect v4 ErrorReporter API (#24445)

  On Effect v4, Sentry.effectLayer now registers a Sentry ErrorReporter. Failures that pass through Effect.withErrorReporting, ErrorReporter.report or the built-in HTTP and RPC reporting boundaries are captured automatically, with ErrorReporter.ignore, ErrorReporter.severity and ErrorReporter.attributes annotations respected. Nothing changes on Effect v3.

Other Changes

• feat(v10/core): Accept a CollectBehavior shorthand for dataCollection.httpHeaders (#24339)
• fix(v10/browser): Release the XHR virtualError once the request completed (#24307)
• fix(v10/browser-utils): Skip nullish LCP entries in vendored web-vitals (#24349)
• fix(v10/bundler-plugins): Stamp debug IDs onto emitted source maps when disable-upload is set (#24332)
• fix(v10/core): Don't instrument the SDK's own envelope requests (#24276)
• fix(v10/nextjs): Only include emitted chunk directories in Turbopack sourcemap upload (#24295)
• fix(v10/nitro): Import from nitro/h3 instead of h3 directly (#24444)
• fix(v10/node-core): Don't recurse in logAndExitProcess on a broken stdio pipe (#24353)
• fix(v10/nuxt): Detect Nitro version via the app's Nuxt dependency chain (#24025)
• fix(v10/replay): Don't rewrite already-emitted nodes when syncing mirror attributes (#23588)

Bundle size 📦

Path	Size
@​sentry/browser	27.18 KB
@​sentry/browser - with treeshaking flags	25.66 KB
@​sentry/browser (incl. Tracing)	45.6 KB
@​sentry/browser (incl. Tracing + Span Streaming)	47.34 KB
@​sentry/browser (incl. Tracing, Profiling)	50.24 KB
@​sentry/browser (incl. Tracing, Replay)	83.99 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking f... Description has been truncated