[dependabot]

Bumps the dev-dependencies group with 21 updates in the / directory:

Package	From	To
@docxodus/export	12.6.2	12.6.5
@playwright/test	1.57.0	1.64.0
@testing-library/jest-dom	6.9.1	7.0.1
@testing-library/react	16.3.2	16.3.3
@testing-library/user-event	14.6.1	14.6.7
@types/node	25.9.5	26.6.5
@vitejs/plugin-react	6.0.3	6.1.2
@vitest/coverage-v8	4.1.10	5.0.3
docxodus	12.6.2	12.6.5
eslint	10.7.0	10.12.0
eslint-plugin-react-refresh	0.5.3	0.5.7
globals	17.7.0	17.13.0
jsdom	29.1.1	30.1.2
react	19.2.7	19.3.0
@types/react	19.2.17	19.3.0
react-dom	19.2.7	19.3.0
@types/react-dom	19.2.3	19.3.0
typescript	6.0.3	7.0.2
typescript-eslint	8.63.0	8.71.1
vite	8.1.4	8.3.4
vitest	4.1.10	5.0.3

Updates @docxodus/export from 12.6.2 to 12.6.5

Release notes

Sourced from @​docxodus/export's releases.

Docxodus 12.6.5

Release notes from the changelog.

Fixed

• DocxDiff now tokenizes Han, kana, and Hangul text by character, so a one-character edit produces a focused redline instead of replacing an entire unspaced phrase (issue #831). Surrogate pairs and attached combining marks remain intact; other text keeps word-level diffs.

• The @docxodus/export CLI now runs when invoked through npm's executable symlink (for example, npx docxodus --help on Linux or macOS). It previously exited with no output because its entry-point check compared the symlink path with the resolved module path. Importing runCli still does not execute the command.

Docxodus 12.6.4 fixes table pagination and indentation, plus malformed list numbering; see the changelog.

Fixed

• A negative table indent (w:tblInd) is no longer clamped to margin-left: 0 (issue #827). Word uses a negative indent to pull an over-wide table into the left margin; the HTML now carries the negative margin, and the paginated view clips page content only vertically, so the table's overhang into either side margin stays visible, as in Word. Right-to-left tables apply the indent on their leading (right) edge.

• Paginated view: a table taller than one page is now split across pages when its only merged cells are horizontal (colspan, which the converter emits for Word's w:gridSpan, e.g. full-width section-header rows) (issue #807). Such tables used to be refused by the row splitter and placed whole in one page box that clips its overflow, so every row past the first page-height was rendered but invisible. The splitter only cuts between rows and copies rows whole, so a colspan can never be cut. Tables with vertical merges (rowspan), nested tables, or footnotes still take the previous whole-block fallback.

• SourceFileCopyrightTests no longer fails because of gitignored files (issue #822). It used to walk every *.cs under the repository root, so a stale scratch checkout under a gitignored directory such as .cache/ failed its checks locally but not in CI. It now scans the files git ls-files reports, both tracked files and new files not yet added. Outside a git checkout, such as a source tarball, it falls back to the directory walk.

• ListItemRetriever.RetrieveListItem no longer throws a NullReferenceException for a paragraph outside the parts list numbering covers (issue #814). Comment paragraphs hit this on every IR read (verification, diff, reversibility proof). Callers swallowed the exception, but each comment paragraph still paid for a throw and a full list re-initialization. It now returns null straight away. Comment paragraphs still get no list marker; that behaviour is now deliberate rather than a side effect of the exception.

• Malformed list numbering no longer makes ListItemRetriever.RetrieveListItem throw (issue #818). Examples are a w:num whose w:abstractNum is missing, a paragraph level with no w:lvl or past the last level, a missing or non-integer attribute in numbering.xml, an empty numbering or styles part, and a counter a number format can't represent. Such a paragraph now gets no list marker. A counter outside a format's range (a negative Roman numeral, say) renders as decimal. DOCX→HTML conversion used

... (truncated)

Changelog

Sourced from @​docxodus/export's changelog.

[12.6.5] - 2026-09-28

Fixed

• DocxDiff now tokenizes Han, kana, and Hangul text by character, so a one-character edit produces a focused redline instead of replacing an entire unspaced phrase (issue #831). Surrogate pairs and attached combining marks remain intact; other text keeps word-level diffs.

• The @docxodus/export CLI now runs when invoked through npm's executable symlink (for example, npx docxodus --help on Linux or macOS). It previously exited with no output because its entry-point check compared the symlink path with the resolved module path. Importing runCli still does not execute the command.

[12.6.4] - 2026-09-28

Fixed

• A negative table indent (w:tblInd) is no longer clamped to margin-left: 0 (issue #827). Word uses a negative indent to pull an over-wide table into the left margin; the HTML now carries the negative margin, and the paginated view clips page content only vertically, so the table's overhang into either side margin stays visible, as in Word. Right-to-left tables apply the indent on their leading (right) edge.

• Paginated view: a table taller than one page is now split across pages when its only merged cells are horizontal (colspan, which the converter emits for Word's w:gridSpan, e.g. full-width section-header rows) (issue #807). Such tables used to be refused by the row splitter and placed whole in one page box that clips its overflow, so every row past the first page-height was rendered but invisible. The splitter only cuts between rows and copies rows whole, so a colspan can never be cut. Tables with vertical merges (rowspan), nested tables, or footnotes still take the previous whole-block fallback.

• SourceFileCopyrightTests no longer fails because of gitignored files (issue #822). It used to walk every *.cs under the repository root, so a stale scratch checkout under a gitignored directory such as .cache/ failed its checks locally but not in CI. It now scans the files git ls-files reports, both tracked files and new files not yet added. Outside a git checkout, such as a source tarball, it falls back to the directory walk.

• ListItemRetriever.RetrieveListItem no longer throws a NullReferenceException for a paragraph outside the parts list numbering covers (issue #814). Comment paragraphs hit this on every IR read (verification, diff, reversibility proof). Callers swallowed the exception, but each comment paragraph still paid for a throw and a full list re-initialization. It now returns null straight away. Comment paragraphs still get no list marker; that behaviour is now deliberate rather than a side effect of the exception.

• Malformed list numbering no longer makes ListItemRetriever.RetrieveListItem throw (issue #818). Examples are a w:num whose w:abstractNum is missing, a paragraph level with no w:lvl or past the last level, a missing or non-integer attribute in numbering.xml, an empty numbering or styles part, and a counter a number format can't represent. Such a paragraph now gets no list marker. A counter outside a format's range (a negative Roman numeral, say) renders as decimal. DOCX→HTML conversion used to fail outright on these documents and now converts them. The IR reader, the markdown

... (truncated)

Commits

• 19b40bd docs(changelog): cut v12.6.5 release notes
• dc1f6b2 chore(release): prepare coordinated 12.6.5 and docx-scalpel 0.6.5 release
• 56c37d3 fix(docxdiff): redline individual CJK characters (#832)
• 7ff894a fix(export): run CLI through npm executable symlinks (#830)
• 8abf08b chore(demo): update CDN examples to Docxodus 12.6.4 (#829)
• 69b4ed3 docs(changelog): cut v12.6.4 release notes
• 08847ee chore(python): bump docx-scalpel to 0.6.4
• 8e80a46 fix(converter): preserve table indents and page-margin overflow (#828)
• b3def3a fix(pagination): split oversized tables whose only merges are horizontal (#826)
• 39e8464 fix(core): keep style indentation on unresolvable list numbering (#821) (#825)
• Additional commits viewable in compare view

Updates @playwright/test from 1.57.0 to 1.64.0

Release notes

Sourced from @​playwright/test's releases.

v1.64.0

🧰 WebMCP

New page.webmcp and frame.webmcp give access to the tools that a page registers through the experimental WebMCP browser API, so you can test them like any other part of your app:

const browser = await chromium.launch({ args: ['--enable-features=WebMCP'] });
const page = await browser.newPage();
await page.goto('https://example.com');
for (const tool of await page.webmcp.tools())
console.log(tool.name, tool.description);
const result = await page.webmcp.callTool('add', { a: 2, b: 40 });
console.log(result.content[0].text); // "42"

Playwright MCP also supports WebMCP by default, with page-defined tools offered to the agent as webmcp_<tool>. Pass --no-webmcp to opt out.

playwright-cli exposes them as well:

playwright-cli webmcp-list
playwright-cli webmcp-call search_catalog --params '{"query":"cats"}'

🎬 Better videos

Videos can now be recorded at a custom frame rate, and the decorations for actions are styled with plain CSS:

// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
use: {
video: {
mode: 'on',
size: { width: 1920, height: 1080 },
fps: 60,
show: {
actions: {
style: {
point: 'width: 20px; height: 20px; border-radius: 50%; background: red',
highlight: 'outline: 2px solid #333; background: rgba(0, 128, 255, .15)',
title: 'font-size: 16px',
},
},
},
},
</tr></table>

... (truncated)

Commits

• 606ecd8 cherry-pick(#43192): fix(locators): parse locators the way the client API bui...
• e4f872c cherry-pick(#43188): feat(api): expose asLocatorDescription via LocalUtils fo...
• f6a439e cherry-pick(#43189): docs(webmcp): expose WebMCP to all languages
• e2335c3 cherry-pick(#43174): fix(mcp): do not close the browser twice when the client...
• d2a436e cherry-pick(#43163): Revert "fix(blob): do not remove existing reports from o...
• a0c4b5e cherry-pick(#43175): feat(api): return language-specific locator code from re...
• 3f7d535 cherry-pick(#43131): docs: fix broken C# samples in API docs and handles guide
• 1cde64f cherry-pick(#43170): fix(locators): parse mixed role options
• 8851e72 cherry-pick(#43171): fix(locators): parse JavaScript escapes and regex classes
• dcc5065 cherry-pick(#43172): fix(locator): parse within and getByRef locators
• Additional commits viewable in compare view

Updates @testing-library/jest-dom from 6.9.1 to 7.0.1

Release notes

Sourced from @​testing-library/jest-dom's releases.

v7.0.1

7.0.1 (2026-08-09)

Bug Fixes

• declare vitest as an optional peer dependency (#733) (3782c78)

v7.0.0

7.0.0 (2026-07-20)

Features

• add toContainAnyBy* and toContainOneBy* query matchers (1e39089)

BREAKING CHANGES

• @​testing-library/dom is now a required peer dependency. The minimum supported Node.js version is now 22.

Repaired release for testing-library/jest-dom#731

v6.10.0

6.10.0 (2026-07-20)

Features

• add toContainAnyBy* and toContainOneBy* query matchers (#731) (cae44df)

Commits

• 3782c78 fix: declare vitest as an optional peer dependency (#733)
• 1e39089 feat: add toContainAnyBy* and toContainOneBy* query matchers
• cae44df feat: add toContainAnyBy* and toContainOneBy* query matchers (#731)
• 55c07ce ci: switch release to npm trusted publishing (#726)
• 213256f docs: move toHaveSelection from the deprecated section (#717)
• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​testing-library/jest-dom since your current version.

Updates @testing-library/react from 16.3.2 to 16.3.3

Release notes

Sourced from @​testing-library/react's releases.

v16.3.3

16.3.3 (2026-08-27)

Bug Fixes

• Avoid act() re-entrant when dispatching events (#1468) (20ce75f)

Commits

• 20ce75f fix: Avoid act() re-entrant when dispatching events (#1468)
• be9d81d docs: fix typos in comments and types (#1446)
• See full diff in compare view

Updates @testing-library/user-event from 14.6.1 to 14.6.7

Release notes

Sourced from @​testing-library/user-event's releases.

v14.6.7

14.6.7 (2026-09-02)

Bug Fixes

• normalize DataTransfer format aliases (#1326) (1e0020b)
• feature: Add iframe support for user.keyboard typing (#1275) (1e0020b)

v14.6.6

14.6.6 (2026-08-22)

Bug Fixes

• default pointer event pointerType to empty string instead of the string "undefined" (#1325) (71a5475)

v14.6.5

14.6.5 (2026-08-18)

Bug Fixes

• tab retargeting if focus moved during keydown (#1296) (43efda7)

v14.6.4

14.6.4 (2026-08-11)

Bug Fixes

• keyboard event repeat property (#1312) (d7e80e3)

v14.6.3

14.6.3 (2026-08-03)

Bug Fixes

• release: manually release a patch version (#1321) (1d18b1f), closes #1317

v14.6.2

14.6.2 (2026-08-03)

Commits

• 1e0020b fix: normalize DataTransfer format aliases (#1326)
• d4b0593 feature: Add iframe support for user.keyboard typing (#1275)
• 71a5475 fix: default pointer event pointerType to empty string instead of the string ...
• 43efda7 fix: tab retargeting if focus moved during keydown (#1296)
• d7e80e3 fix: keyboard event repeat property (#1312)
• 43d8e6c ci: remove broken npm backfill step (#1322)
• 1d18b1f fix(release): manually release a patch version (#1321)
• 232f3e6 docs: add migration note and clean up README badges (#1320)
• 83e2b22 ci: remove deprecated CodeSandbox CI (#1318)
• e8da819 ci: publish to npm via OIDC trusted publishing (#1317)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​testing-library/user-event since your current version.

Updates @types/node from 25.9.5 to 26.6.5

Commits

• See full diff in compare view

Updates @vitejs/plugin-react from 6.0.3 to 6.1.2

Release notes

Sourced from @​vitejs/plugin-react's releases.

plugin-react@6.1.2

Fix HMR for compound components (#1484)

Adding or removing a component from a compound component was not handled, creating stale updates. Doing this now triggers hmr invalidate on the file and propagates the invalidation to importers.

Fix compiler.logDiagnostics option not working (#1483)

With oxc-transform-react >= 0.148, the logDiagnostics was not working. This version fixes it and requires oxc-transform-react >= 0.152 as a peer dependency if you are using the compiler option. compiler.logDiagnostics option is now deprecated and should be swapped for the builtin compiler.reportDiagnostics.

Disable refresh for non-jsx with compiler enabled (fix #1478) (#1485)

When the compiler was enabled, TS files could trigger fast refresh which would cause runtime errors. The logic now follows what the builtin oxc plugin in Vite does.

plugin-react@6.1.1

Add compiler.logDiagnostics option

Recoverable React Compiler diagnostics are no longer logged by default. Set compiler.logDiagnostics to true to log them through Vite. Fatal diagnostics are always logged and fail the transform.

Respect environment sourcemap option for React Compiler transform when builder.sharedPlugins is enabled (#1439)

The React Compiler transform was using the top-level sourcemap option instead of the environment sourcemap option. This caused a problem when the experimental builder.sharedPlugins was enabled.

plugin-react@6.1.0

Add experimental native React Compiler support (#1419)

Add experimental native React Compiler support.

You can use it by installing oxc-transform-react and enabling it via the compiler option:

npm install -D oxc-transform-react

import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
export default defineConfig({
plugins: [
react({ compiler: true })
]
})

plugin-react@6.0.5

Fixed the react compiler preset filter to be linear (#1353)

The improved filter in v6.0.3 was non-linear and caused a performance regression (#1349). The filter was changed to be linear to avoid that.

plugin-react@6.0.4

Fixed $RefreshSig$ is not defined error when running vite dev with NODE_ENV=production

... (truncated)

Changelog

Sourced from @​vitejs/plugin-react's changelog.

6.1.2 (2026-10-05)

Fix HMR for compound components (#1484)

Adding or removing a component from a compound component was not handled, creating stale updates. Doing this now triggers hmr invalidate on the file and propagates the invalidation to importers.

Fix compiler.logDiagnostics option not working (#1483)

With oxc-transform-react >= 0.148, the logDiagnostics was not working. This version fixes it and requires oxc-transform-react >= 0.152 as a peer dependency if you are using the compiler option. compiler.logDiagnostics option is now deprecated and should be swapped for the builtin compiler.reportDiagnostics.

Disable refresh for non-jsx with compiler enabled (fix #1478) (#1485)

When the compiler was enabled, TS files could trigger fast refresh which would cause runtime errors. The logic now follows what the builtin oxc plugin in Vite does.

6.1.1 (2026-08-28)

Add compiler.logDiagnostics option

Recoverable React Compiler diagnostics are no longer logged by default. Set compiler.logDiagnostics to true to log them through Vite. Fatal diagnostics are always logged and fail the transform.

Respect environment sourcemap option for React Compiler transform when builder.sharedPlugins is enabled (#1439)

The React Compiler transform was using the top-level sourcemap option instead of the environment sourcemap option. This caused a problem when the experimental builder.sharedPlugins was enabled.

6.1.0 (2026-08-19)

Add experimental native React Compiler support (#1419)

Add experimental native React Compiler support.

You can use it by installing oxc-transform-react and enabling it via the compiler option:

npm install -D oxc-transform-react

import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
export default defineConfig({
plugins: [
react({ compiler: true })
]
})

6.0.5 (2026-07-30)

Fixed the react compiler preset filter to be linear (#1353)

The improved filter in v6.0.3 was non-linear and caused a performance regression (#1349). The filter was changed to be linear to avoid that.

... (truncated)

Commits

• ac47648 release: plugin-react@6.1.2 (#1491)
• 98277e7 fix(deps): update all non-major dependencies (#1486)
• 12eddea fix(hmr): better handle compound components (#1484)
• 3cfb1d1 fix(plugin-react): fix compiler.logDiagnostics (#1483)
• 6de9915 fix(plugin-react): disable refresh for non-jsx with compiler enabled (#1485)
• ee97d2f fix(deps): update all non-major dependencies (#1445)
• b0a014d chore: use Babel 8 for babel compiler playgrounds (#1460)
• 61b650f fix(deps): update react-related dependencies (#1452)
• 736efe2 chore(deps): update tsdown to v0.23 (#1451)
• 04cac50 release: plugin-react@6.1.1 (#1440)
• Additional commits viewable in compare view

Updates @vitest/coverage-v8 from 4.1.10 to 5.0.3

Release notes

Sourced from @​vitest/coverage-v8's releases.

v5.0.3

   🐞 Bug Fixes

• Isolate result.status between repeats runs  -  by @​hi-ogawa, Hiroshi Ogawa and Codex (GPT-6) in vitest-dev/vitest#11218 (5dbeb)
• Don't print an interceptor warning in browser mode  -  by @​sheremet-va in vitest-dev/vitest#11377 (15cc0)
• Don't retry when test.fails expectedly failed  -  by @​hi-ogawa, Hiroshi Ogawa and Codex (GPT-6) in vitest-dev/vitest#11219 (b2458)
• Scope cache key generators to projects  -  by @​ecoyoung in vitest-dev/vitest#11281 and vitest-dev/vitest#11301 (92ba7)
• browser:
  • Delay server listen until tests start running  -  by @​sheremet-va in vitest-dev/vitest#11366 (7d8ed)
  • Check mock path boundaries  -  by @​saryn17, Ryosei Sato and @​sheremet-va in vitest-dev/vitest#11361 and vitest-dev/vitest#11362 (1c388)
  • Keep config of browser-consumed environments  -  by @​kasperpeulen and Claude in vitest-dev/vitest#11378 (aafc0)
  • Ignore page crash while cancelling  -  by @​sheremet-va in vitest-dev/vitest#11386 (7c367)
  • toMatchScreenshot uses wrong reference on retried tests  -  by @​macarie in vitest-dev/vitest#11393 (c22ab)
• cache:
  • Revalidate imports of cached modules  -  by @​sheremet-va in vitest-dev/vitest#11381 (38f98)
• deps:
  • Pin why-is-node-running to 3.2.1 to avoid users running into ERR_PNPM_TRUST_DOWNGRADE  -  by @​AriPerkkio in vitest-dev/vitest#11403 (f6c9a)
• expect:
  • Pass current equality testers to expect.extend asymmetric matchers  -  by @​hi-ogawa, Hiroshi Ogawa and Claude in vitest-dev/vitest#11401 (3e794)
• jsdom:
  • Support Blob on jsdom 30.1  -  by @​sheremet-va in vitest-dev/vitest#11379 (6c49b)
• pool:
  • Preserve unique pool ids when groupOrder is set  -  by @​mtorp in vitest-dev/vitest#11392 (50312)
• ui:
  • Split-pane handle overlapping iframe  -  by @​macarie in vitest-dev/vitest#11221 (f91db)
• vitest:
  • Remove root temp dir on close  -  by @​abhinav-phi in vitest-dev/vitest#11248 (7c711)
• vm:
  • Do not optimize deps from index.html  -  by @​ezefernandezyf, Hiroshi Ogawa and Codex (GPT-6) in vitest-dev/vitest#11329 and vitest-dev/vitest#11360 (caf28)
  • Don't reuse scripts across vite environments  -  by @​MO2k4, Martin Oehlert and Claude in vitest-dev/vitest#11395 (346d3)

    View changes on GitHub

v5.0.2

   🐞 Bug Fixes

• Bind process in case global is overwritten  -  by @​AriPerkkio in vitest-dev/vitest#11343 (0b792)
• detect-async-leaks:
  • Ignore process.stdio handles  -  by @​AriPerkkio in vitest-dev/vitest#11333 (0fd6b)
• expect:
  • Fix toMatchObject with asymmetric matchers  -  by @​ShreeBohara, Claude Opus 5, @​hi-ogawa, Hiroshi Ogawa and Codex (GPT-5) in vitest-dev/vitest#11100 (42523)
• jsdom:
  • Fix Request with Blob body on jsdom 28+  -  by @​harshit-d3v in vitest-dev/vitest#11295 (d1c3e)
• reporter:
  • agent to respect --silent  -  by @​Raj4478 and @​AriPerkkio in vitest-dev/vitest#11271 (5b95e)
• reporters:
  • Handle concurrent createReport calls  -  by @​7rulnik in vitest-dev/vitest#11278 (e8e55)
  • hanging-process to use ESM entrypoint  -  by @​AriPerkkio in vitest-dev/vitest#11316 (4e91e)
• spy:
  • Fix stack overflow when spying Set.prototype.add  -  by @​fengmk2 in vitest-dev/vitest#11299 (a0a93)

... (truncated)

Commits

• 33cadea chore: release v5.0.3 (#11409)
• a029e76 chore: migrate to oxc (#11367)
• 428e2e5 chore: release v5.0.2 (#11357)
• 03630a5 chore: release v5.0.1 (#11275)
• f441c6f chore: release v5.0.0 (#11130)
• c4473e4 fix(coverage): prevent crash on /@fs/ prepended virtual files (#11119)
• 897f51f chore: release v5.0.0-rc.4 (#11107)
• 7db80dc chore: release v5.0.0-rc.3 (#11089)
• 5f6a5e8 feat(coverage): switch to @vitest/istanbuljs packages (#11053)
• c6174a6 fix(coverage): v8 to ignore Vite SSR's generated import bindings (#11023)
• Additional commits viewable in compare view

Updates docxodus from 12.6.2 to 12.6.5

Release notes

Sourced from docxodus's releases.

Docxodus 12.6.5

Release notes from the changelog.

Fixed

• DocxDiff now tokenizes Han, kana, and Hangul text by character, so a one-character edit produces a focused redline instead of replacing an entire unspaced phrase (issue #831). Surrogate pairs and attached combining marks remain intact; other text keeps word-level diffs.

• The @docxodus/export CLI now runs when invoked through npm's executable symlink (for example, npx docxodus --help on Linux or macOS). It previously exited with no output because its entry-point check compared the symlink path with the resolved module path. Importing runCli still does not execute the command.

Docxodus 12.6.4 fixes table pagination and indentation, plus malformed list numbering; see the changelog.

Fixed

• A negative table indent (w:tblInd) is no longer clamped to margin-left: 0 (issue #827). Word uses a negative indent to pull an over-wide table into the left margin; the HTML now carries the negative margin, and the paginated view clips page content only vertically, so the table's overhang into either side margin stays visible, as in Word. Right-to-left tables apply the indent on their leading (right) edge.

• Paginated view: a table taller than one page is now split across pages when its only merged cells are horizontal (colspan, which the converter emits for Word's w:gridSpan, e.g. full-width section-header rows) (issue #807). Such tables used to be refused by the row splitter and placed whole in one page box that clips its overflow, so every row past the first page-height was rendered but invisible. The splitter only cuts between rows and copies rows whole, so a colspan can never be cut. Tables with vertical merges (rowspan), nested tables, or footnotes still take the previous whole-block fallback.

• SourceFileCopyrightTests no longer fails because of gitignored files (issue #822). It used to walk every *.cs under the repository root, so a stale scratch checkout under a gitignored directory such as .cache/ failed its checks locally but not in CI. It now scans the files git ls-files reports, both tracked files and new files not yet added. Outside a git checkout, such as a source tarball, it falls back to the directory walk.

• ListItemRetriever.RetrieveListItem no longer throws a NullReferenceException for a paragraph outside the parts list numbering covers (issue #814). Comment paragraphs hit this on every IR read (verification, diff, reversibility proof). Callers swallowed the exception, but each comment paragraph still paid for a throw and a full list re-initialization. It now returns null straight away. Comment paragraphs still get no list marker; that behaviour is now deliberate rather than a side effect of the exception.

• Malformed list numbering no longer makes ListItemRetriever.RetrieveListItem throw (issue #818). Examples are a w:num whose w:abstractNum is missing, a paragraph level with no w:lvl or past the last level, a missing or non-integer attribute in numbering.xml, an empty numbering or styles part, and a counter a number format can't represent. Such a paragraph now gets no list marker. A counter outside a format's range (a negative Roman numeral, say) renders as decimal. DOCX→HTML conversion used

... (truncated)

Changelog

Sourced from docxodus's changelog.

[12.6.5] - 2026-09-28

Fixed

• DocxDiff now tokenizes Han, kana, and Hangul text by character, so a one-character edit produces a focused redline instead of replacing an entire unspaced phrase (issue #831). Surrogate pairs and attached combining marks remain intact; other text keeps word-level diffs.

• The @docxodus/export CLI now runs when invoked through npm's executable symlink (for example, npx docxodus --help on Linux or macOS). It previously exited with no output because its entry-point check compared the symlink path with the resolved module path. Importing runCli still does not execute the command.

[12.6.4] - 2026-09-28

Fixed

• A negative table indent (w:tblInd) is no longer clamped to margin-left: 0 (issue #827). Word uses a negative indent to pull an over-wide table into the left margin; the HTML now carries the negative margin, and the paginated view clips page content only vertically, so the table's overhang into either side margin stays visible, as in Word. Right-to-left tables apply the indent on their leading (right) edge.

• Paginated view: a table taller than one page is now split across pages when its only merged cells are horizontal (colspan, which the converter emits for Word's w:gridSpan, e.g. full-width section-header rows) (issue #807). Such tables used to be refused by the row splitter and placed whole in one page box that clips its overflow, so every row past the first page-height was rendered but invisible. The splitter only cuts between rows and copies rows whole, so a colspan can never be cut. Tables with vertical merges (rowspan), nested tables, or footnotes still take the previous whole-block fallback.

• SourceFileCopyrightTests no longer fails because of gitignored files (issue #822). It used to walk every *.cs under the repository root, so a stale scratch checkout under a gitignored directory such as .cache/ failed its checks locally but not in CI. It now scans the files git ls-files reports, both tracked files and new files not yet added. Outside a git checkout, such as a source tarball, it falls back to the directory walk.

• ListItemRetriever.RetrieveListItem no longer throws a NullReferenceException for a paragraph outside the parts list numbering covers (issue #814). Comment paragraphs hit this on every IR read (verification, diff, reversibility proof). Callers swallowed the exception, but each comment paragraph still paid for a throw and a full list re-initialization. It now returns null straight away. Comment paragraphs still get no list marker; that behaviour is now deliberate rather than a side effect of the exception.

• Malformed list numbering no longer makes ListItemRetriever.RetrieveListItem throw (issue #818). Examples are a w:num whose w:abstractNum is missing, a paragraph level with no w:lvl or past the last level, a missing or non-integer attribute in numbering.xml, an empty numbering or styles part, and a counter a number format can't represent. Such a paragraph now gets no list marker. A counter outside a format's range (a negative Roman numeral, say) renders as decimal. DOCX→HTML conversion used to fail outright on these documents and now converts them. The IR reader, the markdown

... (truncated)

Commits

• 19b40bd docs(changelog): cut v12.6.5 release notes
• dc1f6b2 chore(release): prepare coordinated 12.6.5 and docx-scalpel 0.6.5 release
• 56c37d3 fix(docxdiff): redline individual CJK characters (#832)
• 7ff894a fix(export): run CLI through npm executable symlinks (#830)
• 8abf08b chore(demo): update CDN examples to Docxodus 12.6.4 (#829)
• 69b4ed3 docs(changelog): cut v12.6.4 release notes
• 08847ee chore(python): bump docx-scalpel to 0.6.4
• 8e80a46 fix(converter): preserve table indents and page-margin overflow (#828)