chore(deps-dev): bump the development-dependencies group across 1 directory with 4 updates

[dependabot]

Bumps the development-dependencies group with 4 updates in the / directory: @yao-pkg/pkg, esbuild, frog and tsx.

Updates @yao-pkg/pkg from 6.20.0 to 6.22.0

Release notes

Sourced from @​yao-pkg/pkg's releases.

Release 6.22.0

6.22.0 (2026-07-30)

Features

• bump fetch 3.6.5 with nodejs 22.23.2, 24.18.1, 26.5.1 (#291) (e1a96ae)

Bug Fixes

• prelude: throw instead of crashing on Intl.Segmenter with small-icu (#290) (cbc7629)

Chores

• ci: use node 24.x for release, drop npm upgrade step (c1e10f5)

Release 6.21.0

6.21.0 (2026-06-30)

Features

• build hooks (preBuild, postBuild, per-file transform) (#273) (3667383), closes package.json#pkg
• bump fetch 3.6.3 with node 22.22.3, 24.15.0 and 26.2.0 (#277) (546bbf0)
• bump fetch 3.6.4 with nodejs 22.23.1, 24.18.0, 26.4.0 (#288) (3520d26)

Bug Fixes

• detector: pick up six more silent-drop shapes (re-exports, new URL, multi-arg path.join, path.resolve(__dirname,…), createRequire aliases, import.meta.resolve) (#272) (ea66111), closes #269
• sea: set process.pkg in worker threads (#270) (376e2a4)

Test added

• fetch-all: track supported node majors, drop node20 (#286) (1b0002f)
• split unit tests into node:test suite, add c8 coverage (#271) (26f10a3), closes #267 #267

Chores

• add worktrees to gitignore (d585e27)
• deps: bump esbuild to >=0.28.1 to fix security vuln (#282) (#284) (68f41d5)

Changelog

Sourced from @​yao-pkg/pkg's changelog.

6.22.0 (2026-07-30)

Features

• bump fetch 3.6.5 with nodejs 22.23.2, 24.18.1, 26.5.1 (#291) (e1a96ae)

Bug Fixes

• prelude: throw instead of crashing on Intl.Segmenter with small-icu (#290) (cbc7629)

Chores

• ci: use node 24.x for release, drop npm upgrade step (c1e10f5)

6.21.0 (2026-06-30)

Features

• build hooks (preBuild, postBuild, per-file transform) (#273) (3667383), closes package.json#pkg
• bump fetch 3.6.3 with node 22.22.3, 24.15.0 and 26.2.0 (#277) (546bbf0)
• bump fetch 3.6.4 with nodejs 22.23.1, 24.18.0, 26.4.0 (#288) (3520d26)

Bug Fixes

• detector: pick up six more silent-drop shapes (re-exports, new URL, multi-arg path.join, path.resolve(__dirname,…), createRequire aliases, import.meta.resolve) (#272) (ea66111), closes #269
• sea: set process.pkg in worker threads (#270) (376e2a4)

Test added

• fetch-all: track supported node majors, drop node20 (#286) (1b0002f)
• split unit tests into node:test suite, add c8 coverage (#271) (26f10a3), closes #267 #267

Chores

• add worktrees to gitignore (d585e27)
• deps: bump esbuild to >=0.28.1 to fix security vuln (#282) (#284) (68f41d5)

6.19.0 (2026-04-24)

Features

• config: accept CLI-only build flags in pkg config (#263) (a8e91df)

Bug Fixes

• deps: update @​roberts_lando/vfs to version 0.3.3 (#266) (d155e24)
• detector: stop silent dependency drops in SEA mode (ESM parse, dynamic import, decorators) (#268) (81c6c88)
• sea: silence benign LIEF warnings during postject injection (#265) (974df53)

6.18.2 (2026-04-22)

... (truncated)

Commits

• See full diff in compare view

Updates esbuild from 0.28.1 to 0.28.2

Release notes

Sourced from esbuild's releases.

v0.28.2

• Fix tree shaking bug due to TypeScript import alias (#4507)

  This release fixes a bug that could cause esbuild to incorrectly tree-shake imports that are used in a TypeScript type alias under certain circumstances. Affected code uses a TypeScript-specific import assignment and looks something like this:

  import Base from './dep.js';
  import Alias = Base.SomeType;

• Fix CSS minification bug involving & (#4497)

  This release fixes a bug where esbuild's CSS minifier incorrectly removed a & when it was unsafe to do so. Here is an example:

  /* Original code */
  .a .b {
    & .b:not(& .c) {
      color: red;
    }
  }
  /* Old output (with --minify) */
  .a .b{.b:not(& .c){color:red}}
  /* New output (with --minify) */
  .a .b{& .b:not(& .c){color:red}}

  This should match <span class="a"><span class="b"><span class="b">yes</span></span></span> but not <span class="a"><span class="b">no</span></span>. The old output incorrectly matched both.

• Avoid overwriting input files without --allow-overwrite (#4484)

  For example: esbuild input.js --outfile=input.js tells esbuild to overwrite input.js with the output of running esbuild on it. This was supposed to already be prevented by default, but it accidentally regressed in version 0.17.0 and apparently didn't have any test coverage. The error message was being printed but the input file was still being overwritten. Oops.

  This release puts the original behavior back. With this release, esbuild should now actually avoid overwriting input files unless --allow-overwrite is explicitly present. This is done by not writing out any files when a build error is encountered.

• Fix incorrect code generated when using top-level await (#4498)

  Previously esbuild could generate code containing a syntax error in complex scenarios involving top-level await used in a dependency cycle. The problem was a missing async on one or more module wrapper closures. With this release, esbuild now uses a fixed-point iteration algorithm to correctly annotate all dependencies in the cycle as needing an async module wrapper.

• Fix a minification bug with lowered logical assignment operators (#4508)

  This release fixes a bug that could cause esbuild to generate incorrect code for logical assignment operators when lowering them to an older target environment. Specifically the lowering process requires duplicating the left-hand side, but esbuild incorrectly failed to count the duplicate as a new usage when the left-hand side is an identifier. That then caused the minifier to believe that the left-hand side was only used once and could attempt to incorrectly inline an initializer into the first usage. This bug has now been fixed:

  // Original code
  function foo() {
    let x
    bar(x ||= {})

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.28.2

• Fix tree shaking bug due to TypeScript import alias (#4507)

  This release fixes a bug that could cause esbuild to incorrectly tree-shake imports that are used in a TypeScript type alias under certain circumstances. Affected code uses a TypeScript-specific import assignment and looks something like this:

  import Base from './dep.js';
  import Alias = Base.SomeType;

• Fix CSS minification bug involving & (#4497)

  This release fixes a bug where esbuild's CSS minifier incorrectly removed a & when it was unsafe to do so. Here is an example:

  /* Original code */
  .a .b {
    & .b:not(& .c) {
      color: red;
    }
  }
  /* Old output (with --minify) */
  .a .b{.b:not(& .c){color:red}}
  /* New output (with --minify) */
  .a .b{& .b:not(& .c){color:red}}

  This should match <span class="a"><span class="b"><span class="b">yes</span></span></span> but not <span class="a"><span class="b">no</span></span>. The old output incorrectly matched both.

• Avoid overwriting input files without --allow-overwrite (#4484)

  For example: esbuild input.js --outfile=input.js tells esbuild to overwrite input.js with the output of running esbuild on it. This was supposed to already be prevented by default, but it accidentally regressed in version 0.17.0 and apparently didn't have any test coverage. The error message was being printed but the input file was still being overwritten. Oops.

  This release puts the original behavior back. With this release, esbuild should now actually avoid overwriting input files unless --allow-overwrite is explicitly present. This is done by not writing out any files when a build error is encountered.

• Fix incorrect code generated when using top-level await (#4498)

  Previously esbuild could generate code containing a syntax error in complex scenarios involving top-level await used in a dependency cycle. The problem was a missing async on one or more module wrapper closures. With this release, esbuild now uses a fixed-point iteration algorithm to correctly annotate all dependencies in the cycle as needing an async module wrapper.

• Fix a minification bug with lowered logical assignment operators (#4508)

  This release fixes a bug that could cause esbuild to generate incorrect code for logical assignment operators when lowering them to an older target environment. Specifically the lowering process requires duplicating the left-hand side, but esbuild incorrectly failed to count the duplicate as a new usage when the left-hand side is an identifier. That then caused the minifier to believe that the left-hand side was only used once and could attempt to incorrectly inline an initializer into the first usage. This bug has now been fixed:

  // Original code
  function foo() {
    let x

... (truncated)

Commits

• 609683d publish 0.28.2 to npm
• 11b1fe4 add to release notes
• ab50d91 css: fix green/blue channel swap in oklch gamut mapping (#4488)
• 04627b6 fix #4498: async TLA checks need a worklist
• 5c15177 disable gopls in the go folder
• fc2ee9b css: adjust parser to allow --foo: {...}
• 209db54 release notes for css nesting bugfix
• c625d31 fix #4497: preserve nested ampersands during minification (#4500)
• 34474e2 better isolation of current part in js parser
• 07f6e8c fix #4507: import assignment tree-shaking bug
• Additional commits viewable in compare view

Updates frog from 1.0.15 to 1.1.0

Release notes

Sourced from frog's releases.

frog@1.1.0

Minor Changes

• 5225ab5: Added pluggable friction stores, a Postgres.js-backed Store.postgres({ connectionString }) factory, and the Frog.create logging API.

  import { Frog, Store } from 'frog'
  const store = Store.postgres({ connectionString: process.env.DATABASE_URL! })
  const frog = Frog.create({ store })
  await frog.log({
  body: 'The workaround used.',
  severity: 'minor',
  title: 'Tool required a workaround',
  })
  const logs = await frog.logs()
  await store.close()

Changelog

Sourced from frog's changelog.

1.1.0

Minor Changes

• 5225ab5: Added pluggable friction stores, a Postgres.js-backed Store.postgres({ connectionString }) factory, and the Frog.create logging API.

  import { Frog, Store } from 'frog'
  const store = Store.postgres({ connectionString: process.env.DATABASE_URL! })
  const frog = Frog.create({ store })
  await frog.log({
  body: 'The workaround used.',
  severity: 'minor',
  title: 'Tool required a workaround',
  })
  const logs = await frog.logs()
  await store.close()

Commits

• 702c4ea fix: preserve release note formatting (#79)
• 7b71c09 chore: version packages (#77)
• d3b008e docs: simplify database overview (#78)
• 5225ab5 feat: add pluggable friction stores (#75)
• 94ed2a8 docs: add typescript agent conventions (#76)
• See full diff in compare view

Updates tsx from 4.22.4 to 4.23.13

Release notes

Sourced from tsx's releases.

v4.23.13

4.23.13 (2026-08-30)

Bug Fixes

• cache: bound shared transform cache memory (#835) (28e1f12)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.23.12

4.23.12 (2026-08-10)

Bug Fixes

• shim import.meta when tokens are split by comments or newlines (#829) (ed9d330), closes #828

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.23.11

4.23.11 (2026-08-07)

Bug Fixes

• preserve async ESM require fallback (55cbece)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.23.10

4.23.10 (2026-08-07)

Bug Fixes

• support nyc coverage discovery (#710) (ec1bcd5)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.23.9

4.23.9 (2026-08-06)

... (truncated)

Commits

• 28e1f12 fix(cache): bound shared transform cache memory (#835)
• ed9d330 fix: shim import.meta when tokens are split by comments or newlines (#829)
• 651f5be test: cover CommonJS TypeScript import.meta paths
• bd3bc64 test: cover CommonJS loader source fallback
• 55cbece fix: preserve async ESM require fallback
• 6c5ba85 docs: document CommonJS default interop
• ec1bcd5 fix: support nyc coverage discovery (#710)
• b6e5b48 docs: clarify CommonJS default imports
• 2f55884 fix: map Node test locations
• de935d5 docs: document Node source-map stack formatting
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	tsx@​4.22.4 ⏵ 4.23.13			+1
	frog@​1.0.15 ⏵ 1.1.0	+3		+1	+1
	@​yao-pkg/​pkg@​6.20.0 ⏵ 6.22.0			+1	+5

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Recently published: npm content-type published 3 days ago Location: Package overview From: pnpm-lock.yaml → npm/frog@1.1.0 → npm/content-type@3.1.0 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/content-type@3.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: npm nanoid published 4 days ago Location: Package overview From: pnpm-lock.yaml → npm/vitest@4.1.8 → npm/vite-plus@0.1.24 → npm/nanoid@3.3.19 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/nanoid@3.3.19. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: npm yaml published 3 days ago Location: Package overview From: pnpm-lock.yaml → npm/vitest@4.1.8 → npm/vite-plus@0.1.24 → npm/frog@1.1.0 → npm/yaml@2.9.1 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yaml@2.9.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report