3 hours ago
KaTeX

v0.18.3

0.18.3 (2026-08-09)

Bug Fixes

3 hours ago
docx-editor

@docx-editor.dev/editor-api@2.2.0

Patch Changes

  • Updated dependencies [3096225]
  • Updated dependencies [9c25492]
  • Updated dependencies [04c2379]
  • Updated dependencies [f0e4ab9]
    • @docx-editor.dev/core@2.2.0
3 hours ago
docx-editor

@docx-editor.dev/core@2.2.0

Minor Changes

  • 3096225: The document now fits its container by default, so a narrow window shrinks the page instead of overflowing it and opening the comments pane shrinks the document rather than pushing it off screen. Drive it with Editor.setZoomMode or React's new useZoom hook, and pass zoomMode={{ type: 'fixed' }} to keep the old behavior.

Patch Changes

  • 9c25492: Keep legacy FORMTEXT result text editable with character-accurate caret and selection offsets.
  • 04c2379: Programmatic selections made while embedded fonts load now keep their range and visible highlight after the shaped-font remount.
  • f0e4ab9: Tracked changes on a field's result now render as tracked. A deletion or insertion around the value of a cross-reference, page number or form field previously painted as ordinary unchanged text, so a reviewer saw no strikethrough or author colour on an edit the review sidebar was reporting correctly. A paragraph containing such a field also measured longer than what was laid out from it, which put the caret and the keystroke at different offsets — clicking after the field placed the cursor in one place and typing appeared in another. w:fldSimple now paints its cached result instead of blank space, allowlisted PAGE/NUMPAGES/SECTIONPAGES nested inside a non-page simple field evaluate per sheet rather than reusing the saved cache, and field results carry Word's grey field shading — always for legacy form fields unless the document sets w:doNotShadeFormData, and per the new fieldShading option (never / when-selected / always) for the rest.
  • Updated dependencies [568ccf7]
    • @docx-editor.dev/i18n@2.2.0
3 hours ago
docx-editor

@docx-editor.dev/react@2.2.0

Minor Changes

  • 568ccf7: Localizing the editor now works the way the docs describe it. <DocxEditor> takes an i18n prop, so a locale no longer needs a LocaleProvider around it; a provider still works and now composes when nested instead of resetting the subtree to English. The toolbar's overflow panel also labels its value rows (zoom, line spacing, the style, font and colour pickers) from the active catalogue rather than showing the raw i18n key.

Patch Changes

  • a4d7885: <DocxEditor>'s title bar and toolbar now sit on one --doc-surface band, closed by a hairline and a soft shadow directly under the toolbar, with the ruler row and the workspace below it on --doc-bg. The seam used to be a border under the title bar, which split the band in two and left the toolbar edge to edge on no ground of its own: the toolbar paints a rounded pill, so flush against the frame its radius never showed and the row read as a second flat bar. Hosts were adding their own wrapper to get the packaged chrome to look like the composed demo it is modelled on. Nothing about the API changes, and both surfaces follow the dark palette as before.
  • Updated dependencies [568ccf7]
    • @docx-editor.dev/i18n@2.2.0
3 hours ago
docx-editor

@docx-editor.dev/i18n@2.2.0

Minor Changes

  • 568ccf7: The catalogue drops 456 keys nothing renders, mostly strings for dialogs that no longer ship, and every community locale is pruned to match. TranslationKey and LocaleStrings narrow accordingly, so naming a removed key is now a type error rather than a lookup that returned nothing visible.
8 hours ago
router

Release 2026-08-09 09:07

Release 2026-08-09 09:07

Changes

Performance

  • router-core: skip impossible JSON parse attempts (#8006) (44a8c3e1d2) by @Sheraff
  • start-client-core: O(1) buffer drain in client frame decoder (#8009) (c59788ca20) by @Sheraff
  • router-core: faster enumerable-key collection in structural sharing (#8010) (5253e70db2) by @Sheraff

Packages

  • @tanstack/react-router@1.170.24
  • @tanstack/react-start@1.168.41
  • @tanstack/react-start-client@1.168.22
  • @tanstack/react-start-rsc@0.1.40
  • @tanstack/react-start-server@1.167.29
  • @tanstack/router-cli@1.167.26
  • @tanstack/router-core@1.171.20
  • @tanstack/router-generator@1.167.26
  • @tanstack/router-plugin@1.168.28
  • @tanstack/router-vite-plugin@1.167.28
  • @tanstack/solid-router@1.170.23
  • @tanstack/solid-start@1.168.40
  • @tanstack/solid-start-client@1.168.22
  • @tanstack/solid-start-server@1.167.29
  • @tanstack/start-client-core@1.170.20
  • @tanstack/start-plugin-core@1.171.32
  • @tanstack/start-server-core@1.169.24
  • @tanstack/start-static-server-functions@1.167.25
  • @tanstack/start-storage-context@1.167.22
  • @tanstack/vue-router@1.170.22
  • @tanstack/vue-start@1.168.39
  • @tanstack/vue-start-client@1.167.25
  • @tanstack/vue-start-server@1.167.29
8 hours ago
router

@tanstack/vue-start-server@1.167.29

Patch Changes

  • Updated dependencies [44a8c3e, 5253e70]:
    • @tanstack/router-core@1.171.20
    • @tanstack/start-server-core@1.169.24
    • @tanstack/vue-router@1.170.22
8 hours ago
router

@tanstack/vue-start@1.168.39

Patch Changes

  • Updated dependencies [c59788c]:
    • @tanstack/start-client-core@1.170.20
    • @tanstack/start-plugin-core@1.171.32
    • @tanstack/start-server-core@1.169.24
    • @tanstack/vue-router@1.170.22
    • @tanstack/vue-start-client@1.167.25
    • @tanstack/vue-start-server@1.167.29