Skip to content

Bump the npm-dependencies group across 1 directory with 16 updates#914

Closed
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/npm-dependencies-0cd54c14e0
Closed

Bump the npm-dependencies group across 1 directory with 16 updates#914
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/npm-dependencies-0cd54c14e0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Jan 2, 2026

Bumps the npm-dependencies group with 14 updates in the / directory:

Package From To
@tailwindcss/cli 4.1.17 4.1.18
esbuild 0.25.12 0.27.2
glob 11.0.3 13.0.0
rollup 4.53.2 4.54.0
@cloudflare/vitest-pool-workers 0.9.14 0.11.1
@eslint/js 9.39.1 9.39.2
@npmcli/arborist 9.1.6 9.1.9
@vitest/coverage-istanbul 3.2.4 4.0.16
@vitest/coverage-v8 3.2.4 4.0.16
eslint 9.39.1 9.39.2
globals 16.5.0 17.0.0
lerna 9.0.0 9.0.3
prettier 3.6.2 3.7.4
vitest 3.2.4 4.0.16

Updates @tailwindcss/cli from 4.1.17 to 4.1.18

Release notes

Sourced from @​tailwindcss/cli's releases.

v4.1.18

Fixed

  • Ensure validation of source(…) happens relative to the file it is in (#19274)
  • Include filename and line numbers in CSS parse errors (#19282)
  • Skip comments in Ruby files when checking for class names (#19243)
  • Skip over arbitrary property utilities with a top-level ! in the value (#19243)
  • Support environment API in @tailwindcss/vite (#18970)
  • Preserve case of theme keys from JS configs and plugins (#19337)
  • Write source maps correctly on the CLI when using --watch (#19373)
  • Handle special defaults (like ringColor.DEFAULT) in JS configs (#19348)
  • Improve backwards compatibility for content theme key from JS configs (#19381)
  • Upgrade: Handle future and experimental config keys (#19344)
  • Try to canonicalize any arbitrary utility to a bare value (#19379)
  • Validate candidates similarly to Oxide (#19397)
  • Canonicalization: combine text-* and leading-* classes (#19396)
  • Correctly handle duplicate CLI arguments (#19416)
  • Don’t emit color-mix fallback rules inside @keyframes (#19419)
  • CLI: Don't hang when output is /dev/stdout (#19421)
Changelog

Sourced from @​tailwindcss/cli's changelog.

[4.1.18] - 2025-12-11

Fixed

  • Ensure validation of source(…) happens relative to the file it is in (#19274)
  • Include filename and line numbers in CSS parse errors (#19282)
  • Skip comments in Ruby files when checking for class names (#19243)
  • Skip over arbitrary property utilities with a top-level ! in the value (#19243)
  • Support environment API in @tailwindcss/vite (#18970)
  • Preserve case of theme keys from JS configs and plugins (#19337)
  • Write source maps correctly on the CLI when using --watch (#19373)
  • Handle special defaults (like ringColor.DEFAULT) in JS configs (#19348)
  • Improve backwards compatibility for content theme key from JS configs (#19381)
  • Upgrade: Handle future and experimental config keys (#19344)
  • Try to canonicalize any arbitrary utility to a bare value (#19379)
  • Validate candidates similarly to Oxide (#19397)
  • Canonicalization: combine text-* and leading-* classes (#19396)
  • Correctly handle duplicate CLI arguments (#19416)
  • Don’t emit color-mix fallback rules inside @keyframes (#19419)
  • CLI: Don't hang when output is /dev/stdout (#19421)

[3.4.19] - 2025-12-10

Fixed

  • Don’t break sibling-*() functions when used inside calc(…) (#19335)
Commits
Maintainer changes

This version was pushed to npm by malfaitrobin, a new releaser for @​tailwindcss/cli since your current version.


Updates esbuild from 0.25.12 to 0.27.2

Release notes

Sourced from esbuild's releases.

v0.27.2

  • Allow import path specifiers starting with #/ (#4361)

    Previously the specification for package.json disallowed import path specifiers starting with #/, but this restriction has recently been relaxed and support for it is being added across the JavaScript ecosystem. One use case is using it for a wildcard pattern such as mapping #/* to ./src/* (previously you had to use another character such as #_* instead, which was more confusing). There is some more context in nodejs/node#49182.

    This change was contributed by @​hybrist.

  • Automatically add the -webkit-mask prefix (#4357, #4358)

    This release automatically adds the -webkit- vendor prefix for the mask CSS shorthand property:

    /* Original code */
    main {
      mask: url(x.png) center/5rem no-repeat
    }
    /* Old output (with --target=chrome110) */
    main {
    mask: url(x.png) center/5rem no-repeat;
    }
    /* New output (with --target=chrome110) */
    main {
    -webkit-mask: url(x.png) center/5rem no-repeat;
    mask: url(x.png) center/5rem no-repeat;
    }

    This change was contributed by @​BPJEnnova.

  • Additional minification of switch statements (#4176, #4359)

    This release contains additional minification patterns for reducing switch statements. Here is an example:

    // Original code
    switch (x) {
      case 0:
        foo()
        break
      case 1:
      default:
        bar()
    }
    // Old output (with --minify)
    switch(x){case 0:foo();break;case 1:default:bar()}
    // New output (with --minify)

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.27.2

  • Allow import path specifiers starting with #/ (#4361)

    Previously the specification for package.json disallowed import path specifiers starting with #/, but this restriction has recently been relaxed and support for it is being added across the JavaScript ecosystem. One use case is using it for a wildcard pattern such as mapping #/* to ./src/* (previously you had to use another character such as #_* instead, which was more confusing). There is some more context in nodejs/node#49182.

    This change was contributed by @​hybrist.

  • Automatically add the -webkit-mask prefix (#4357, #4358)

    This release automatically adds the -webkit- vendor prefix for the mask CSS shorthand property:

    /* Original code */
    main {
      mask: url(x.png) center/5rem no-repeat
    }
    /* Old output (with --target=chrome110) */
    main {
    mask: url(x.png) center/5rem no-repeat;
    }
    /* New output (with --target=chrome110) */
    main {
    -webkit-mask: url(x.png) center/5rem no-repeat;
    mask: url(x.png) center/5rem no-repeat;
    }

    This change was contributed by @​BPJEnnova.

  • Additional minification of switch statements (#4176, #4359)

    This release contains additional minification patterns for reducing switch statements. Here is an example:

    // Original code
    switch (x) {
      case 0:
        foo()
        break
      case 1:
      default:
        bar()
    }
    // Old output (with --minify)
    switch(x){case 0:foo();break;case 1:default:bar()}

... (truncated)

Commits
  • cd83297 publish 0.27.2 to npm
  • 2759721 additional tests for switch with break
  • fd2b4b3 update release notes
  • c8d93a7 fix #4357: -webkit- prefix for mask shorthand (#4358)
  • 92ff12c compat table: update @types/node
  • a35eceb compat table: fix a type error with the new types
  • f598984 fix make compat-table to install dependencies
  • f7f6df0 release notes for #4361
  • 6f8ec15 fix: allow subpath imports that start with #/ (#4361)
  • f7ae61f minify some switch statements to if-else statement
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for esbuild since your current version.


Updates glob from 11.0.3 to 13.0.0

Changelog

Sourced from glob's changelog.

changeglob

13

  • Move the CLI program out to a separate package, glob-bin. Install that if you'd like to continue using glob from the command line.

12

  • Remove the unsafe --shell option. The --shell option is now ONLY supported on known shells where the behavior can be implemented safely.

11.1

GHSA-5j98-mcp5-4vw2

  • Add the --shell option for the command line, with a warning that this is unsafe. (It will be removed in v12.)
  • Add the --cmd-arg/-g as a way to safely add positional arguments to the command provided to the CLI tool.
  • Detect commands with space or quote characters on known shells, and pass positional arguments to them safely, avoiding shell:true execution.

11.0

  • Drop support for node before v20

10.4

  • Add includeChildMatches: false option
  • Export the Ignore class

10.3

  • Add --default -p flag to provide a default pattern
  • exclude symbolic links to directories when follow and nodir are both set

10.2

  • Add glob cli

10.1

  • Return '.' instead of the empty string '' when the current working directory is returned as a match.
  • Add posix: true option to return / delimited paths, even on

... (truncated)

Commits

Updates rollup from 4.53.2 to 4.54.0

Release notes

Sourced from rollup's releases.

v4.54.0

4.54.0

2025-12-20

Features

  • Enable tree-shaking for Symbol.hasInstance, Symbol.dispose and Symbol.asyncDispose properties if unused (#6046)

Bug Fixes

  • Ensure that well-known-Symbol-valued properties are not tree-shaken except in select cases (#6046)
  • Ensure namespace properties are included when referenced only from a try-catch (#6216)

Pull Requests

v4.53.5

4.53.5

2025-12-16

Bug Fixes

  • Fix wrong semicolon insertion position when using JSX (#6206)
  • Generate spec-compliant sourcemaps when sources content is excluded (#6196)

Pull Requests

v4.53.4

4.53.4

2025-12-15

Bug Fixes

  • Ensure Symbol.dispose and Symbol.asyncDispose properties are never removed with (await) using declarations. (#6209)

Pull Requests

... (truncated)

Changelog

Sourced from rollup's changelog.

4.54.0

2025-12-20

Features

  • Enable tree-shaking for Symbol.hasInstance, Symbol.dispose and Symbol.asyncDispose properties if unused (#6046)

Bug Fixes

  • Ensure that well-known-Symbol-valued properties are not tree-shaken except in select cases (#6046)
  • Ensure namespace properties are included when referenced only from a try-catch (#6216)

Pull Requests

4.53.5

2025-12-16

Bug Fixes

  • Fix wrong semicolon insertion position when using JSX (#6206)
  • Generate spec-compliant sourcemaps when sources content is excluded (#6196)

Pull Requests

4.53.4

2025-12-15

Bug Fixes

  • Ensure Symbol.dispose and Symbol.asyncDispose properties are never removed with (await) using declarations. (#6209)

Pull Requests

... (truncated)

Commits

Updates tailwindcss from 4.1.17 to 4.1.18

Release notes

Sourced from tailwindcss's releases.

v4.1.18

Fixed

  • Ensure validation of source(…) happens relative to the file it is in (#19274)
  • Include filename and line numbers in CSS parse errors (#19282)
  • Skip comments in Ruby files when checking for class names (#19243)
  • Skip over arbitrary property utilities with a top-level ! in the value (#19243)
  • Support environment API in @tailwindcss/vite (#18970)
  • Preserve case of theme keys from JS configs and plugins (#19337)
  • Write source maps correctly on the CLI when using --watch (#19373)
  • Handle special defaults (like ringColor.DEFAULT) in JS configs (#19348)
  • Improve backwards compatibility for content theme key from JS configs (#19381)
  • Upgrade: Handle future and experimental config keys (#19344)
  • Try to canonicalize any arbitrary utility to a bare value (#19379)
  • Validate candidates similarly to Oxide (#19397)
  • Canonicalization: combine text-* and leading-* classes (#19396)
  • Correctly handle duplicate CLI arguments (#19416)
  • Don’t emit color-mix fallback rules inside @keyframes (#19419)
  • CLI: Don't hang when output is /dev/stdout (#19421)
Changelog

Sourced from tailwindcss's changelog.

[4.1.18] - 2025-12-11

Fixed

  • Ensure validation of source(…) happens relative to the file it is in (#19274)
  • Include filename and line numbers in CSS parse errors (#19282)
  • Skip comments in Ruby files when checking for class names (#19243)
  • Skip over arbitrary property utilities with a top-level ! in the value (#19243)
  • Support environment API in @tailwindcss/vite (#18970)
  • Preserve case of theme keys from JS configs and plugins (#19337)
  • Write source maps correctly on the CLI when using --watch (#19373)
  • Handle special defaults (like ringColor.DEFAULT) in JS configs (#19348)
  • Improve backwards compatibility for content theme key from JS configs (#19381)
  • Upgrade: Handle future and experimental config keys (#19344)
  • Try to canonicalize any arbitrary utility to a bare value (#19379)
  • Validate candidates similarly to Oxide (#19397)
  • Canonicalization: combine text-* and leading-* classes (#19396)
  • Correctly handle duplicate CLI arguments (#19416)
  • Don’t emit color-mix fallback rules inside @keyframes (#19419)
  • CLI: Don't hang when output is /dev/stdout (#19421)

[3.4.19] - 2025-12-10

Fixed

  • Don’t break sibling-*() functions when used inside calc(…) (#19335)
Commits

Updates @cloudflare/vitest-pool-workers from 0.9.14 to 0.11.1

Release notes

Sourced from @​cloudflare/vitest-pool-workers's releases.

@​cloudflare/vitest-pool-workers@​0.11.1

Patch Changes

@​cloudflare/vitest-pool-workers@​0.11.0

Minor Changes

  • #11533 8d9003e Thanks @​petebacondarwin! - Add support for ctx.exports

    It is now possible to access ctx.exports properties for the main (SELF) worker.

    • Integration tests: in the SELF worker the ctx.exports object now contains the expected stubs to the exported entry-points.
    • Unit tests: the object returned from createExecutionContext() has exports property that exposes the exports of the SELF worker.

    Due to the dynamic nature of Vitest the integration relies upon guessing what the exports of the main Worker are by statically analyzing the Worker source using esbuild. In cases where it is not possible to infer the exports (for example, a wildcard re-export of a virtual module) it is possible to declare these in the vitest-pool-workers config via the additionalExports setting.

Patch Changes

@​cloudflare/vitest-pool-workers@​0.10.15

Patch Changes

@​cloudflare/vitest-pool-workers@​0.10.14

Patch Changes

@​cloudflare/vitest-pool-workers@​0.10.13

Patch Changes

  • Updated dependencies [59534ba, 7e80340]:
    • miniflare@4.20251202.0
    • wrangler@4.52.1

@​cloudflare/vitest-pool-workers@​0.10.12

Patch Changes

... (truncated)

Changelog

Sourced from @​cloudflare/vitest-pool-workers's changelog.

0.11.1

Patch Changes

0.11.0

Minor Changes

  • #11533 8d9003e Thanks @​petebacondarwin! - Add support for ctx.exports

    It is now possible to access ctx.exports properties for the main (SELF) worker.

    • Integration tests: in the SELF worker the ctx.exports object now contains the expected stubs to the exported entry-points.
    • Unit tests: the object returned from createExecutionContext() has exports property that exposes the exports of the SELF worker.

    Due to the dynamic nature of Vitest the integration relies upon guessing what the exports of the main Worker are by statically analyzing the Worker source using esbuild. In cases where it is not possible to infer the exports (for example, a wildcard re-export of a virtual module) it is possible to declare these in the vitest-pool-workers config via the additionalExports setting.

Patch Changes

0.10.15

Patch Changes

0.10.14

Patch Changes

0.10.13

Patch Changes

  • Updated dependencies [59534ba, 7e80340]:
    • miniflare@4.20251202.0
    • wrangler@4.52.1

... (truncated)

Commits

Updates @eslint/js from 9.39.1 to 9.39.2

Release notes

Sourced from @​eslint/js's releases.

v9.39.2

Bug Fixes

  • 5705833 fix: warn when eslint-env configuration comments are found (#20381) (sethamus)

Build Related

  • 506f154 build: add .scss files entry to knip (#20391) (Milos Djermanovic)

Chores

  • 7ca0af7 chore: upgrade to @eslint/js@9.39.2 (#20394) (Francesco Trotta)
  • c43ce24 chore: package.json update for @​eslint/js release (Jenkins)
  • 4c9858e ci: add v9.x-dev branch (#20382) (Milos Djermanovic)
Commits

Updates @npmcli/arborist from 9.1.6 to 9.1.9

Release notes

Sourced from @​npmcli/arborist's releases.

arborist: v9.1.9

9.1.9 (2025-12-09)

Bug Fixes

arborist: v9.1.8

9.1.8 (2025-11-25)

Bug Fixes

Bumps the npm-dependencies group with 14 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@tailwindcss/cli](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/@tailwindcss-cli) | `4.1.17` | `4.1.18` |
| [esbuild](https://github.com/evanw/esbuild) | `0.25.12` | `0.27.2` |
| [glob](https://github.com/isaacs/node-glob) | `11.0.3` | `13.0.0` |
| [rollup](https://github.com/rollup/rollup) | `4.53.2` | `4.54.0` |
| [@cloudflare/vitest-pool-workers](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/vitest-pool-workers) | `0.9.14` | `0.11.1` |
| [@eslint/js](https://github.com/eslint/eslint/tree/HEAD/packages/js) | `9.39.1` | `9.39.2` |
| [@npmcli/arborist](https://github.com/npm/cli/tree/HEAD/workspaces/arborist) | `9.1.6` | `9.1.9` |
| [@vitest/coverage-istanbul](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-istanbul) | `3.2.4` | `4.0.16` |
| [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) | `3.2.4` | `4.0.16` |
| [eslint](https://github.com/eslint/eslint) | `9.39.1` | `9.39.2` |
| [globals](https://github.com/sindresorhus/globals) | `16.5.0` | `17.0.0` |
| [lerna](https://github.com/lerna/lerna/tree/HEAD/packages/lerna) | `9.0.0` | `9.0.3` |
| [prettier](https://github.com/prettier/prettier) | `3.6.2` | `3.7.4` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `3.2.4` | `4.0.16` |



Updates `@tailwindcss/cli` from 4.1.17 to 4.1.18
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.1.18/packages/@tailwindcss-cli)

Updates `esbuild` from 0.25.12 to 0.27.2
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.25.12...v0.27.2)

Updates `glob` from 11.0.3 to 13.0.0
- [Changelog](https://github.com/isaacs/node-glob/blob/main/changelog.md)
- [Commits](isaacs/node-glob@v11.0.3...v13.0.0)

Updates `rollup` from 4.53.2 to 4.54.0
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.53.2...v4.54.0)

Updates `tailwindcss` from 4.1.17 to 4.1.18
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.1.18/packages/tailwindcss)

Updates `@cloudflare/vitest-pool-workers` from 0.9.14 to 0.11.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/vitest-pool-workers/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/@cloudflare/vitest-pool-workers@0.11.1/packages/vitest-pool-workers)

Updates `@eslint/js` from 9.39.1 to 9.39.2
- [Release notes](https://github.com/eslint/eslint/releases)
- [Commits](https://github.com/eslint/eslint/commits/v9.39.2/packages/js)

Updates `@npmcli/arborist` from 9.1.6 to 9.1.9
- [Release notes](https://github.com/npm/cli/releases)
- [Changelog](https://github.com/npm/cli/blob/latest/workspaces/arborist/CHANGELOG.md)
- [Commits](https://github.com/npm/cli/commits/arborist-v9.1.9/workspaces/arborist)

Updates `@vitest/coverage-istanbul` from 3.2.4 to 4.0.16
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.16/packages/coverage-istanbul)

Updates `@vitest/coverage-v8` from 3.2.4 to 4.0.16
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.16/packages/coverage-v8)

Updates `eslint` from 9.39.1 to 9.39.2
- [Release notes](https://github.com/eslint/eslint/releases)
- [Commits](eslint/eslint@v9.39.1...v9.39.2)

Updates `globals` from 16.5.0 to 17.0.0
- [Release notes](https://github.com/sindresorhus/globals/releases)
- [Commits](sindresorhus/globals@v16.5.0...v17.0.0)

Updates `lerna` from 9.0.0 to 9.0.3
- [Release notes](https://github.com/lerna/lerna/releases)
- [Changelog](https://github.com/lerna/lerna/blob/main/packages/lerna/CHANGELOG.md)
- [Commits](https://github.com/lerna/lerna/commits/v9.0.3/packages/lerna)

Updates `prettier` from 3.6.2 to 3.7.4
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](prettier/prettier@3.6.2...3.7.4)

Updates `vitest` from 3.2.4 to 4.0.16
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.16/packages/vitest)

Updates `wrangler` from 4.44.0 to 4.56.0
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.56.0/packages/wrangler)

---
updated-dependencies:
- dependency-name: "@tailwindcss/cli"
  dependency-version: 4.1.18
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: esbuild
  dependency-version: 0.27.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: glob
  dependency-version: 13.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: npm-dependencies
- dependency-name: rollup
  dependency-version: 4.54.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: tailwindcss
  dependency-version: 4.1.18
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: "@cloudflare/vitest-pool-workers"
  dependency-version: 0.11.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: "@eslint/js"
  dependency-version: 9.39.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: "@npmcli/arborist"
  dependency-version: 9.1.9
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: "@vitest/coverage-istanbul"
  dependency-version: 4.0.16
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: npm-dependencies
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 4.0.16
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: npm-dependencies
- dependency-name: eslint
  dependency-version: 9.39.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: globals
  dependency-version: 17.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: npm-dependencies
- dependency-name: lerna
  dependency-version: 9.0.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: prettier
  dependency-version: 3.7.4
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: vitest
  dependency-version: 4.0.16
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: npm-dependencies
- dependency-name: wrangler
  dependency-version: 4.56.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jan 2, 2026
@dependabot dependabot Bot requested a review from jbampton as a code owner January 2, 2026 02:22
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jan 2, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 2, 2026

Thanks for your first pull request! We appreciate your contribution.

@deepsource-io
Copy link
Copy Markdown

deepsource-io Bot commented Jan 2, 2026

Here's the code health analysis summary for commits a56a50c..687e6b3. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource Python LogoPython✅ SuccessView Check ↗
DeepSource Secrets LogoSecrets✅ SuccessView Check ↗
DeepSource Shell LogoShell✅ SuccessView Check ↗
DeepSource Docker LogoDocker✅ SuccessView Check ↗
DeepSource JavaScript LogoJavaScript✅ SuccessView Check ↗

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

@socket-security
Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm markdown-it is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: package-lock.jsonnpm/@11ty/eleventy@3.1.2npm/markdown-it@14.1.0

ℹ Read more on: This package | This alert | What is obfuscated code?

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 not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/markdown-it@14.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.

Warn Medium
Low adoption: npm obug

Location: Package overview

From: package-lock.jsonnpm/@vitest/coverage-istanbul@4.0.16npm/@vitest/coverage-v8@4.0.16npm/obug@2.1.1

ℹ Read more on: This package | This alert | What are unpopular packages?

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: Unpopular packages may have less maintenance and contain other problems.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/obug@2.1.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

"@cloudflare/vitest-pool-workers": "^0.11.1",
"vitest": "~4.0.16",
"wrangler": "^4.24.0"
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The vitest upgrade to v4.x is incompatible with the existing configuration, which uses the removed coverage.all option. This will cause test and coverage commands to fail.
Severity: CRITICAL | Confidence: High

🔍 Detailed Analysis

The pull request upgrades vitest to version 4.x, which introduces a breaking change by removing the coverage.all configuration option. The project's Vitest configuration files, such as packages/cfsite/vitest.config.js and vite.config.js, still use all: true within the coverage block. When test or coverage commands like npm run coverage are executed, Vitest v4 will encounter this unrecognized option, leading to a validation error and causing the command to fail. This will break the test suite and prevent coverage reports from being generated.

💡 Suggested Fix

Remove the coverage.all: true option from all Vitest configuration files. To replicate the previous behavior of including all source files in the report, add a coverage.include property with glob patterns that explicitly target all relevant source files.

🤖 Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: packages/cfsite/package.json#L16

Potential issue: The pull request upgrades `vitest` to version 4.x, which introduces a
breaking change by removing the `coverage.all` configuration option. The project's
Vitest configuration files, such as `packages/cfsite/vitest.config.js` and
`vite.config.js`, still use `all: true` within the `coverage` block. When test or
coverage commands like `npm run coverage` are executed, Vitest v4 will encounter this
unrecognized option, leading to a validation error and causing the command to fail. This
will break the test suite and prevent coverage reports from being generated.

Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 8095428

@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Jan 15, 2026

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Jan 15, 2026
@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/npm-dependencies-0cd54c14e0 branch January 15, 2026 06:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code root

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants