[dependabot]

Bumps the development-dependencies group with 19 updates in the / directory:

Package	From	To
@changesets/cli	3.0.2	3.0.3
@types/node	24.13.4	24.19.2
fallow	3.24.1	3.35.0
lint-staged	17.5.1	17.6.0
oxfmt	0.67.0	0.74.0
@rollup/plugin-terser	1.0.0	1.0.2
@rollup/plugin-typescript	12.3.0	12.3.1
@types/chrome	0.2.9	0.3.6
postcss	8.5.28	8.5.31
puppeteer	25.10.0	25.16.0
rollup	4.63.1	4.65.0
svelte	5.57.0	5.57.2
vitest	5.0.0	5.0.5
web-ext	10.6.0	10.8.0
@sveltejs/adapter-static	3.0.10	4.0.0
@sveltejs/kit	2.70.3	3.1.0
@sveltejs/vite-plugin-svelte	7.3.0	7.3.1
svelte-check	4.7.6	4.7.7
vite	8.3.0	8.3.5

Updates @changesets/cli from 3.0.2 to 3.0.3

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​3.0.3

Patch Changes

• #2297 3f163da Thanks @​Andarist! - Fixed semver ranges (such as >=1.0.0 <2.0.0) getting cut off (>=2.0.0) when updating internal dependencies.

• #2276 ca9d110 Thanks @​Andarist! - Fixed pnpm 10 compatibility with npm 12 when reading registry information, packing, and publishing packages.

• Updated dependencies [3f163da, bfe9050, e522996]:

  • @​changesets/apply-release-plan@​8.1.1
  • @​changesets/config@​4.0.1

Changelog

Sourced from @​changesets/cli's changelog.

3.0.3

Patch Changes

• #2297 3f163da Thanks @​Andarist! - Fixed semver ranges (such as >=1.0.0 <2.0.0) getting cut off (>=2.0.0) when updating internal dependencies.

• #2276 ca9d110 Thanks @​Andarist! - Fixed pnpm 10 compatibility with npm 12 when reading registry information, packing, and publishing packages.

• Updated dependencies [3f163da, bfe9050, e522996]:

  • @​changesets/apply-release-plan@​8.1.1
  • @​changesets/config@​4.0.1

Commits

• c9269c0 Version Packages (#2291)
• ca9d110 Fix pnpm 10 publishing with npm 12 (#2276)
• 7be7fde Build(deps): Bump the production-dependencies group across 1 directory with 6...
• b430ce0 Move e2e tests to an on-demand workspace (#2275)
• 93314a8 test: add happy path tests for add (#2289)
• d13a39e test: use inline snapshots for publish plan tests (#2284)
• See full diff in compare view

Updates @types/node from 24.13.4 to 24.19.2

Commits

• See full diff in compare view

Updates fallow from 3.24.1 to 3.35.0

Release notes

Sourced from fallow's releases.

v3.35.0: worsened complexity in audit, Vite+ and Egg.js plugins, mutation progress

Features

• fallow audit reports inherited complexity findings that got worse. A complexity finding from the base snapshot is now worsened when its cyclomatic, cognitive, CRAP or line count value is higher than at the base. CRAP counts only when both sides have a score. The line count must grow by at least 5 lines, so a short comment or a formatter rewrap keeps a finding inherited. A function that grows from 80 to 300 lines with the same complexity values is now worsened. The JSON output adds attribution to each complexity finding, worsened_metrics to each finding with a grown value, and attribution.worsened and attribution.complexity_worsened. The human, compact and markdown output add a "Worse than base" section. SARIF and CodeClimate show the values, and the GitHub summary marks each finding as worsened. The --worsened flag and the audit.worsened config key select the effect: warn (default, exit code 0), error (counts like an introduced finding) or off (only growth of an exceeded metric is worsened). The GitHub Action has a worsened input, the GitLab template has FALLOW_AUDIT_WORSENED, and the MCP audit tool has a worsened parameter.

• The VS Code extension has a fallow.audit.worsened setting. The values are warn, error and off, the same as fallow audit --worsened. The default auto uses audit.worsened from the project config. The extension sends the flag only to a CLI that supports it. With an older CLI, the audit runs without the flag and the output channel shows a note.

• A human fallow mutation run shows phase progress on stderr. The lines name the runner setup, the baseline run and the mutant runs with done and total counts. They also name the retries, the final worktree check and the report. A long phase prints a line at a fixed interval, also in non-TTY output, so a slow run does not look stalled. --quiet and --format json print no progress lines, and stdout does not change. The programmatic API has run_mutation_with_progress with MutationProgress events. (#3599)

• fallow mutation --runner-config <path> selects the Vitest config of a run. A project that keeps its integration, UI or browser tests in a separate Vitest config can now run mutants against those tests. The mutation.runnerConfig config key sets the same file, and the flag wins. The file must exist inside the project root, and only the Vitest runner accepts it. A static test file that the selected config does not include stays visible as a test-files-not-discovered error. --config still selects the Fallow config. (#3598)

• Mutation JSON shows the edit of each mutant and the history of each retry. Each mutant in the mutation report and the mutation-plan document has a change object, for example {"from": "??", "to": "&&"}. The values come from a fixed vocabulary of operator tokens, literals and placeholders, so the report still holds no source text (#3658). A retried mutant has a new attempts array with the status, the duration and the killing test, failure kind or runtime-error reason of each run. You can now see if a flaky result was timeout -> survived or survived -> killed (#3656).

• fallow mutation mutates fluent chains in module-level const initializers. The new removed-chain-link operator removes one call link of a chain. For example, z.number().int().positive() gives a mutant without .int() and a mutant without .positive(). A validation schema with no literal or operator now has mutants. The operator is on by default, and --operators and mutation.operators accept its name. (#3662)

• Fallow reads Vite+ projects. A vite-plus dependency, or a root vite.config.* that imports vite-plus, enables the new vite-plus plugin. The pack.entry values are entry points, and the lint.jsPlugins, lint.overrides[].jsPlugins and lint.extends packages count as used. The vite-plus dependency also enables the Vitest plugin. The vp, vpr and vpx binaries credit vite-plus. Fallow reads vp test -c <file>, vp exec <binary> and vp run <task>. It also reads the commands of the staged and run.tasks blocks and the .vite-hooks/ scripts. The file targets of vp lint and vp fmt are not entry points. A vi.mock call through vite-plus/test counts as a Vitest mock.

• Fallow detects Egg.js and tegg projects. The new egg plugin activates on egg, @eggjs/core or @eggjs/tegg, or on an egg, eggPlugin or eggModule key in package.json. Entry points are the files that the Egg loader loads by convention: app.js, agent.js, the router, controllers, services, middleware, extensions, schedules and config files, also in nested example and test fixture apps. Every file of a tegg module is an entry point. The plugin credits the packages that config/plugin.* names, the egg.framework package and the default egg framework to the package.json that owns the app.

• Fallow reads the entry files of a JavaScript GitHub Action. When action.yml or action.yaml sets runs.using to a node runtime, the runs.pre, runs.main and runs.post files are entry points. A path in dist/ maps to its source file, with the same rules as a package.json main field. A composite or Docker action adds no entry points.

• A dead-code baseline records if node_modules existed. A --save-baseline run writes analysis_identity.node_modules as present or missing. A later run in the other install state adds a baseline-install-state-mismatch entry to workspace_diagnostics and prints a warning, also under --quiet. Findings that need installed packages can differ between the two states, so such a run can report baseline findings as new.

• External plugins can opt a config pattern out of the default export credit. List the pattern in configDefaultExportOptOut when the tool reads named exports, or when the pattern also matches ordinary source files.

• Fallow reports a missing workspace directory and analyzes nested pnpm projects. A positive workspace pattern whose directory does not exist now gets the workspace-pattern-dir-missing diagnostic, with degrades_analysis: true. While such a pattern exists, the run does not report unused-catalog-entries for any catalog, because the missing packages can use catalog entries. This also applies to a pattern for a directory that does not exist yet, such as packages/* in a template. A directory that exists but holds no package does not turn off the check. Create the directory before the run or remove the pattern to get the check back. A directory with its own package.json and pnpm-workspace.yaml that no root pattern declares is an independent pnpm project. Fallow analyzes it as a workspace and reports the information-only nested-project-root diagnostic. (#3710)

• Each release publishes a CycloneDX SBOM for every target. The files are named fallow-<target>.cdx.json. .vex/openvex.json states why fallow is not affected by each advisory that the repository ignores. SECURITY.md lists the supported versions and the code scanning policy.

Changed

• fallow audit --gate new-only reports growth of an already exceeded complexity metric as worsened. Before, such a finding was introduced. A function that exceeded a threshold on the base and grows a little in the PR no longer fails the audit by default. With the default audit.worsened: warn, the verdict is warn and the exit code is 0. The finding stays introduced when the growth moves it to a higher severity tier. It also stays introduced when it now exceeds a metric that it did not exceed on the base, and that metric grew. The exceeded flags and the tier come from the base run. A threshold override in the same PR does not make an old finding introduced.

• fallow audit --gate new-only no longer fails on a CRAP score from estimated coverage alone. Without a coverage map, fallow estimates CRAP from static test reachability, and this estimate does not measure the change. A finding that exceeds only the CRAP threshold with estimated coverage now has effective_severity: warn and SARIF level warning. A finding that also exceeds the cyclomatic or cognitive threshold still gates. CRAP from measured coverage still gates, and --gate all does not change.

• fallow audit no longer fails on a complexity finding in a test file. A long it(...) or describe(...) callback often exceeds the cognitive threshold. Such a finding now has effective_severity: warn and the new field gate_exemption: "test-file", with a verdict of at least warn and exit code 0. This applies to --gate new-only and --gate all. The human, markdown and compact views list these findings under "Test files, not gated". fallow health does not change. (#3753)

• The GitHub Action requests the branded token only when it posts. The token step now runs only on a pull_request event with comment: true or review-comments: true. The branded-token input now defaults to auto. auto posts as the Fallow app when the workflow grants id-token: write. Without that permission, it falls back to github-token without a log line. An explicit branded-token: true keeps one short fallback line, and false behaves as before. (#3755)

• --type-aware class-member refinement is faster on large projects. The symbol-use scan now checks the name first and keeps one alias answer for each symbol. On a large TypeScript project, the scan takes 4 to 12 s instead of 35 to 70 s, with the same decisions. The scan now also sends only the names that a query can reach to the checker for TypeScript files. JavaScript files keep the full scan, because require bindings also create aliases. (#3765)

• fallow mutation with Vitest isolate: false no longer repeats the setup of unrelated test files. Each static mutant runs in a new runner process, and that process now dry-runs only the test files that cover the mutant. A covering test that fails its dry run is still a baseline failure. (#3650)

• The fallow skill shows the review loop that fallow checks. One short example runs fallow audit, reads the walkthrough guide, writes a judgment, and validates it with --walkthrough-file. The example saves the guide and the judgment in the temporary folder, because a new file in the project tree makes the judgment stale.

Bug fixes

• fallow mutation makes fewer equivalent mutants. No test can kill these mutants, so they no longer appear:
  • an empty-string or swapped-boolean case label with the same body as default, only when all labels are literals and both bodies exit unconditionally (#3639);
  • i != N for the test of a counted for loop with an integer let counter and no other write (#3649);

... (truncated)

Commits

• 1f5a08d chore: release v3.35.0
• 96c3b10 chore(deps): bump follow-redirects from 1.16.0 to 1.16.1 in /editors/vscode i...
• e950d68 chore(deps-dev): bump follow-redirects (#3726)
• d2d3671 ci: skip the pull request title lint for bot pull requests (#3774)
• d6e6fb7 ci: check Dependabot merge list fields before a merge (#3773)
• d01e42c ci: keep Dependabot squash subjects within 100 characters (#3772)
• ab193e8 perf(type-aware): send only reachable identifiers to the checker (#3765)
• cb91b1e docs: name plugin_credits in the skill and the entry export credit for plugin...
• a0a15ce docs: note that config discovery probes ancestor directories (#3769)
• 6aa0d63 ci: drop sign-off trailers from Dependabot repair commits (#3768)
• Additional commits viewable in compare view

Updates lint-staged from 17.5.1 to 17.6.0

Release notes

Sourced from lint-staged's releases.

v17.6.0

Minor Changes

• #1850 938d3f4 - Task functions like { title, task } can now use a logger function log() to emit output while the task runs. By default, the output will only be visible if the task fails, unless the --verbose option was used. Additionally, when the task rejects, the error will be shown in the output.

  import { defineConfig } from 'lint-staged/config'
  export default defineConfig({
  '*': {
  title: 'Fail if PDF files are committed',
  task: async (filepaths, { log }) => {
  const pdfFiles = filepaths.filter((f) => f.toLowerCase().endsWith('.pdf'))
  if (pdfFiles.length > 0) {
  log('PDF files should not be committed: %s', pdfFiles)
  throw new Error('Failed')
  }
  },
  },
  })

• #1854 30562bc - lint-staged now stages changes to all tracked files modified by tasks, including files that weren’t originally staged or didn’t match the configured globs. This can happen when your task has side-effects, or it's a function that ignores the staged files like () => "prettier --write .".

  If you have unstaged changes in a file and the task also edits that file, your unstaged changes will be staged too. Use --hide-unstaged to hide your changes while tasks run.

Patch Changes

• #1860 4296532 - The assignment of staged files to lint-staged configuration files (when using multiple, for example in a monorepo) has been rewritten to be more efficient. As a reminder, each staged file is assigned to exactly one configuration (the closest one), even if that config doesn't match the file in its globs.

• #1861 c45f28a - Fix running parallel tasks for a single glob, when tasks are created by a function. Nesting one level of arrays inside an array of tasks will result in the inner tasks running in parallel. This behavior should now be consistent when creating tasks using functions. In the following example eslint and prettier will run in parallel (for all files, when any JS files are staged):

  import { defineConfig } from 'lint-staged/config'
  export default defineConfig({
  '*.js': () => [['eslint --max-warnings=0 .', 'prettier --list-different .']],
  })

• #1859 f0ea69d - Various performance improvements from skipping redundant internal Git calls.

• #1856 69d7d17 - Partially staged changes are hidden in a uniquely-named patch file to avoid multiple invocations of lint-staged overwriting it. This makes it safer to run lint-staged in multiple worktrees at the same time.

Changelog

Sourced from lint-staged's changelog.

17.6.0

Minor Changes

• #1850 938d3f4 - Task functions like { title, task } can now use a logger function log() to emit output while the task runs. By default, the output will only be visible if the task fails, unless the --verbose option was used. Additionally, when the task rejects, the error will be shown in the output.

  import { defineConfig } from 'lint-staged/config'
  export default defineConfig({
  '*': {
  title: 'Fail if PDF files are committed',
  task: async (filepaths, { log }) => {
  const pdfFiles = filepaths.filter((f) => f.toLowerCase().endsWith('.pdf'))
  if (pdfFiles.length > 0) {
  log('PDF files should not be committed: %s', pdfFiles)
  throw new Error('Failed')
  }
  },
  },
  })

• #1854 30562bc - lint-staged now stages changes to all tracked files modified by tasks, including files that weren’t originally staged or didn’t match the configured globs. This can happen when your task has side-effects, or it's a function that ignores the staged files like () => "prettier --write .".

  If you have unstaged changes in a file and the task also edits that file, your unstaged changes will be staged too. Use --hide-unstaged to hide your changes while tasks run.

Patch Changes

• #1860 4296532 - The assignment of staged files to lint-staged configuration files (when using multiple, for example in a monorepo) has been rewritten to be more efficient. As a reminder, each staged file is assigned to exactly one configuration (the closest one), even if that config doesn't match the file in its globs.

• #1861 c45f28a - Fix running parallel tasks for a single glob, when tasks are created by a function. Nesting one level of arrays inside an array of tasks will result in the inner tasks running in parallel. This behavior should now be consistent when creating tasks using functions. In the following example eslint and prettier will run in parallel (for all files, when any JS files are staged):

  import { defineConfig } from 'lint-staged/config'
  export default defineConfig({
  '*.js': () => [['eslint --max-warnings=0 .', 'prettier --list-different .']],
  })

• #1859 f0ea69d - Various performance improvements from skipping redundant internal Git calls.

• #1856 69d7d17 - Partially staged changes are hidden in a uniquely-named patch file to avoid multiple invocations of lint-staged overwriting it. This makes it safer to run lint-staged in multiple worktrees at the same time.

Commits

• 48f9f4e Merge pull request #1857 from lint-staged/changeset-release/main
• 16b2e21 chore(changeset): release
• 195f156 docs: improve changeset
• 0ba6261 fix: create hidden directory only when required
• 66ac2de docs: fixes to changesets
• 80af8d7 Merge pull request #1863 from lint-staged/fix-issues
• e433488 fix: handle task editing a symlinked file to a regular file, and --fail-on-ch...
• e5019b3 fix: handle trailing newlines when detecting changed files
• 74efec8 ci: run Cygwin and MSYS2 tests on Node.js 26
• 655b7dc fix: use TypeScript types instead of JSDoc
• Additional commits viewable in compare view

Updates oxfmt from 0.67.0 to 0.74.0

Release notes

Sourced from oxfmt's releases.

oxfmt v0.74.0

🐛 Bug Fixes

• e236de0 formatter_tests: Skip conformance spec calls with non-literal options (#27957) (leaysgur)
• 782ab6e linter: Search string values without UTF-8 conversion (#26716) (Dunqing)
• a5d8184 jsdoc: Parse code spans after quotes in descriptions (#27955) (leaysgur)
• 2645d2c formatter_markdown: Treat link destinations and footnote references as opaque to code span fences (#27948) (leaysgur)
• 4d8195c formatter_yaml: Keep a root plain scalar starting with a document marker verbatim (#27947) (leaysgur)
• 529b057 formatter_core: Keep front matter verbatim when body starts with indented delimiter (#27946) (leaysgur)
• c22a9b2 formatter: Treat static block with only empty statements as empty (#27945) (leaysgur)
• d3ff3f6 formatter/jsdoc: Write descriptions as written to not close the comment (#27823) (leaysgur)
• c4c1727 formatter/sort_imports: Keep comments after the last import (#27822) (leaysgur)
• a64677e formatter: Print JSDoc embedded snippets with LF (#27821) (leaysgur)
• 2c1cc20 formatter: Keep comment only Vue bindings as-is (#27820) (leaysgur)
• 1bf236d formatter/sort_imports: Do not use comments as import source (#27819) (leaysgur)
• 52ee29d formatter_yaml: Never start col-0 line with document marker or BOM (#27818) (leaysgur)
• 81c75e7 formatter/css: Keep glued css-in-js statement placeholders glued (#27814) (leaysgur)
• a1ef7f4 formatter: Keep typecast parens in same-operator binary and arrow chain (#27812) (leaysgur)
• de110ce formatter: Keep more parens around TSInstantiationExpression (#27811) (leaysgur)
• 8b02e90 formatter_json: Reject invalid JSON instead of dropping them (#27785) (leaysgur)
• 6fe4c1b formatter: Treat lone CR in JSX text and argument blank lines (#27780) (leaysgur)
• 5605362 oxfmt: Validate editorconfig as like oxfmtrc (#27778) (leaysgur)
• 5b2acb0 formatter_core: Report error position releative to CRLF source (#27777) (leaysgur)
• c78e80e formatter_core: Report parse error positions relative to the BOM-headed source (#27776) (leaysgur)
• 3a980c9 formatter_toml: Handle BOM like other languages (#27775) (leaysgur)
• 97c9fc4 oxfmt: Handle BOM in config JSON (#27774) (leaysgur)
• 28eb4a7 oxfmt: Print trailing newline for --list-different (#27773) (leaysgur)
• d2bea21 formatter: Glue comments to an opener in empty for-head slots and array holes (#27737) (leaysgur)
• 6a95ec1 formatter: Keep comment position on holey array (#27730) (leaysgur)
• 54769da formatter: Break after dangling line comment in holey array (#27729) (leaysgur)
• 99077ef formatter_json: Reject unary expressions other than signed numbers (#27728) (leaysgur)
• 22cd4cd formatter_json: Handle holey array and comments (#27727) (leaysgur)
• 644ca1c formatter: Do not indent logical chains whose right sides all inline (#27667) (leaysgur)
• a07a0fb formatter: Wrap comment-only JSX expression container in a group (#27666) (leaysgur)

⚡ Performance

• e220293 formatter: Check only the operator suppression mark in is_quiet (#27952) (leaysgur)
• e5fdc9c formatter_core: Write into one element stack through a concrete Formatter (#27559) (leaysgur)
• a342f7e formatter: Skip comment handling for nodes with no comment near them (#27557) (leaysgur)
• d8ce750 formatter: Write string literals with swapped quotes into the arena (#27558) (Yuji Sugiura)
• 1c393c0 formatter_core: Skip scanning texts with nothing to rewrite (#27561) (leaysgur)
• 1d3ef10 formatter_core: Keep the embedded IR when nothing in it is rewritten (#27673) (leaysgur)

📚 Documentation

• 1325225 oxfmt: Update useless comment prefix (#27956) (leaysgur)
• d0dd140 formatter: Note lossy cooked round-trip in template embeds (#27944) (leaysgur)
• 8a3a6c8 oxfmt: Update stale notes on the JSDoc string-out channel and fixture origins (#27824) (leaysgur)

... (truncated)

Changelog

Sourced from oxfmt's changelog.

Changelog

All notable changes to this package will be documented in this file.

The format is based on Keep a Changelog.

[0.73.0] - 2026-10-13

🚀 Features

• a495e82 oxfmt: Support associations config to specify language over filepath (#27437) (leaysgur)
• 5db28fa oxfmt: Support Astro via prettier-plugin-astro@1.x (#27386) (leaysgur)

📚 Documentation

• 408d87f oxfmt: Simplify oxfmtrc docs (#27432) (leaysgur)
• 902e188 oxfmt: Update how embeddedLanguageFormatting option works (#27362) (leaysgur)

Commits

• 07ed78f release(apps): oxlint v1.89.0 && oxfmt v0.74.0 (#27961)
• 6941b4e release(apps): oxlint v1.88.0 && oxfmt v0.73.0 (#27643)
• a495e82 feat(oxfmt): support associations config to specify language over filepath ...
• 408d87f docs(oxfmt): simplify oxfmtrc docs (#27432)
• 5db28fa feat(oxfmt): support Astro via prettier-plugin-astro@1.x (#27386)
• 902e188 docs(oxfmt): update how embeddedLanguageFormatting option works (#27362)
• 2bd08eb release(apps): oxlint v1.87.0 && oxfmt v0.72.0 (#27341)
• 2ae2939 release(apps): oxlint v1.86.0 && oxfmt v0.71.0 (#27132)
• f158bff chore(deps): update npm packages (#26865)
• 288d8cc release(apps): oxlint v1.85.0 && oxfmt v0.70.0 (#26903)
• Additional commits viewable in compare view

Updates @rollup/plugin-terser from 1.0.0 to 1.0.2

Changelog

Sourced from @​rollup/plugin-terser's changelog.

v1.0.2

2026-10-21

Updates

• terser: update terser to ^5.49.2 (#2019)

v1.0.1

2026-10-21

Bugfixes

• terser: share nameCache between chunks by serializing minify tasks (#2020)

Commits

• See full diff in compare view

Updates @rollup/plugin-typescript from 12.3.0 to 12.3.1

Changelog

Sourced from @​rollup/plugin-typescript's changelog.

v12.3.1

2026-10-21

Bugfixes

• typescript: clear the pending program update when a build closes the watch program (#2025)

Commits

• 7d2f6e4 chore(release): typescript v12.3.1
• 79dce0e fix(typescript): clear the pending program update when a build closes the wat...
• 5800bf3 chore(repo): test migration to vitest. phase 4 (#1978)
• 7d22981 chore(repo): add rollup-plugin keyword in package.json (#1955)
• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​rollup/plugin-typescript since your current version.

Updates @types/chrome from 0.2.9 to 0.3.6

Commits

• See full diff in compare view

Updates postcss from 8.5.28 to 8.5.31

Release notes

Sourced from postcss's releases.

8.5.31

• Fix better source map on </style> escaping (by @​firefoxic).

8.5.30

• Fix broken map on </style> escaping (by @​Rufflet).

8.5.29

• Improved </style> escaping (by @​choudhryfrompak).
• Fixed comments support in list.comma() and list.space() (by @​00200200).
• Fixed semicolon and custom property (by @​wahidrizka).

Changelog

Sourced from postcss's changelog.

8.5.31

• Fix better source map on </style> escaping (by @​firefoxic).

8.5.30

• Fix broken map on </style> escaping (by @​Rufflet).

8.5.29

• Improved </style> escaping (by @​choudhryfrompak).
• Fixed comments support in list.comma() and list.space() (by @​00200200).
• Fixed semicolon and custom property (by @​wahidrizka).

Commits

• d190857 Release 8.5.31 version
• 4ef6d8c Update dependencies
• 6abd674 Call the builder with every node when the output is escaped (#2175)
• f1aca7e Release 8.5.30 version
• 9d83445 Update dependencies
• 6c9bc73 Fix invalid source map mapping on escaping before new line (#2169)
• 1fd8f88 Add missed changes in changelog
• a7a1f34 Release 8.5.29 version
• b55a36d Update dependencies
• 7647a81 Escape </style> in output of non-Root nodes (#2163)
• Additional commits viewable in compare view

Updates puppeteer from 25.10.0 to 25.16.0

Release notes

Sourced from puppeteer's releases.

puppeteer-core: v25.16.0

25.16.0 (2026-10-22)

🎉 Features

• network: support unmodified post data via HTTPRequest.content() and decode base64 post data (#15585) (ee2a8de)
• roll to Chrome 156.0.8078.47 (#15621) (48705f6)

🛠️ Fixes

• bidi: accept page ranges without spaces in Page.pdf() (#15628) (49372d1)
• bidi: update request headers on response and error events (#15612) (611b320)
• cdp: destroy replaced service_worker target when re-installing an extension (#15614) (e6686fb)
• cdp: fall back to blockedReason when loadingFailed errorText is empty (#15624) (66ee3ea)
• cdp: ignore fileChooserOpened events without backendNodeId (#15625) (2bd58eb)
• cdp: skip undefined header values in HTTPRequest.respond() (#15595) (4dd58bc)
• connect: report permission denied when DevToolsActivePort fails with EPERM/EACCES (#15615) (64ee541)
• locators: reject read-only elements and unaccepted values in Locator.fill (#15603) (46cfff5)
• log browser WebSocket transport errors (#15519) (027927b)
• make deleteMatchingCookies respect domain, path, url and partitionKey (#15581) (deab4f3)
• network: intercept requests on the session that paused them (#15605) (68ae9b8)
• network: return post data of a paused request without asking Chrome (#15607) (c7fcd9a)
• pdf: use exact CSS unit ratios in unitToPixels and respect lengthUnit for default paper size (#15611) (ba0fdea)
• respect the navigation timeout after a follow-up navigation (#15488) (bd227ce)
• return null from SerializedAXNode.elementHandle() after a navigation (#15634) (244e68c)
• roll to Firefox 158.0.1 (#15619) (6fde1bd)
• webdriver: type an apostrophe for the Quote key (#15622) (69f1b57)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​puppeteer/browsers bumped from 3.2.5 to 3.2.6

puppeteer: v25.16.0

25.16.0 (2026-10-22)

🎉 Features

• roll to Chrome 156.0.8078.47 (#15621) (48705f6)

Dependencies

• The following workspace dependencies were updated
  • dependencies

... (truncated)

Commits

• a207faf chore: release main (#15610)
• 244e68c fix: return null from SerializedAXNode.elementHandle() after a navigation (#1...
• 0a4eb48 chore: fix docs link and file name of PR title workflow (#15635)
• 69f1b57 fix(webdriver): type an apostrophe for the Quote key (#15622)
• 0afe136 chore(deps): bump modern-tar from 0.8.5 to 0.8.6 in the dependencies group (#...
• 6b1848d chore(deps-dev): bump rollup from 4.64.6 to 4.64.7 in the dev-dependencies gr...
• 49372d1 fix(bidi): accept page ranges without spaces in Page.pdf() (#15628)
• ca12a3b chore(deps-dev): bump the dev-dependencies group with 4 updates (#15626)
• ee2a8de feat(network): support unmodified post data via HTTPRequest.content() and dec...
• 027927b fix: log browser WebSocket transport errors (#15519)
• Additional commits viewable in compare view

Updates rollup from 4.63.1 to 4.65.0

Release notes

Sourced from rollup's releases.

v4.65.0

4.65.0

2026-10-22

Features

• Support synthetic named exports in namespaces when preserving modules (#6589)

Bug Fixes

• Fix a situation where unaligned sourcemaps resulted in a wrong segment (#6591)
• Forward startup errors on native module load when starting rollup (#6592)

Pull Requests

• #6589: Merge synthetic named exports into static namespaces when preserving modules (@​b84330808, @​lukastaegert)
• #6590: Stabilize flaky watch test "treats filenames literally, not as globs" (@​lukastaegert)
• #6591: Use the last sourcemap segment for log locations after its start (@​Dev-next-gen)
• #6592: Preserve native module load errors (@​shuaiyafei, @​lukastaegert)
• #6593: Close bundles in the Gulp examples (@​shuaiyafei,...

  Description has been truncated

[changeset-bot]

⚠️ No Changeset found

Latest commit: cd65f63

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

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

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