Skip to content

build(deps-dev): bump @cloudflare/vitest-plugin from 1.4.11 to 1.8.1 - #34

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/cloudflare/vitest-plugin-1.8.1
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/cloudflare/vitest-plugin-1.8.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown

Bumps @cloudflare/vitest-plugin from 1.4.11 to 1.8.1.

Release notes

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

@​cloudflare/vitest-plugin@​1.8.1

Patch Changes

  • #16833 5f539b5 Thanks @​jamesopstad! - Name cf commands and settings in remote bindings errors

    When remote bindings could not authenticate, the error told you to run wrangler whoami, wrangler logout and wrangler login. It now names cf auth whoami, cf auth logout and cf auth login. When a Flagship binding without an id needed to run remotely, the error named Wrangler's app_id setting and suggested wrangler flagship apps create. It now names id and suggests cf flagship apps create.

    For the Vitest plugin, this applies to projects that load cloudflare.config.ts. Projects that use a Wrangler configuration file still see the Wrangler commands.

  • #16834 8e57331 Thanks @​edmundhung! - Fix test files never finishing when a socket read rejects after a Worker handler has answered

    Previously, if a handler finished while a socket was still being read, for example a database client's connection, the read's rejection could leave vitest run waiting forever after the tests passed. Vitest now reports the unhandled error and the run ends.

  • Updated dependencies [8b2a363, 5f539b5, dc47e6d, 575d136, 3626ee8]:

@​cloudflare/vitest-plugin@​1.8.0

Minor Changes

  • #16682 5966749 Thanks @​ghostwriternr! - Run the Containers that cloudflare.config.ts attaches to Durable Objects

    Previously, projects that load cloudflare.config.ts through the config option ran those Durable Objects without their Containers. The plugin now prepares the Containers' images and runs them, as it does for Wrangler configuration files. Dockerfile and build context paths are relative to the directory that contains cloudflare.config.ts.

    cloudflare.config.ts has no setting that disables local Containers, so, as with the Vite plugin, projects with Container-backed Durable Objects need Docker to run their tests.

Patch Changes

  • #16824 877b249 Thanks @​jamesopstad! - Move streaming tail consumers to experimental.streamingTailConsumers in cloudflare.config.ts

    Streaming Tail Workers are now declared in a separate, experimental list instead of with streaming: true on a tailConsumers entry. tailConsumers now only lists Tail Workers with a tail() handler. This is a breaking change to the experimental config API: move each entry that set streaming: true to experimental.streamingTailConsumers, without the streaming field.

    export default defineConfig({
      worker: {
        tailConsumers: [{ worker: "tail-worker" }],
        experimental: {
          streamingTailConsumers: [{ worker: "streaming-tail-worker" }],
        },
      },
    });

    Fields under experimental may change or be removed without a major version bump. The wrangler-to-cf codemod now converts streaming_tail_consumers to experimental.streamingTailConsumers.

  • #16734 c47cca7 Thanks @​matingathani! - Fix CommonJS dependencies being loaded as ES modules under Vitest 5 inline projects

    A dependency with its own "type": "commonjs" package.json was treated as an ES module when an earlier .js file elsewhere in the project had been classified by the project's "type": "module" package.json. The dependency then failed at import with errors such as Cannot set properties of undefined or exports is not defined. The nearest package.json now always decides how a .js file is loaded.

  • Updated dependencies [877b249, 69e650c]:

... (truncated)

Changelog

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

1.8.1

Patch Changes

  • #16833 5f539b5 Thanks @​jamesopstad! - Name cf commands and settings in remote bindings errors

    When remote bindings could not authenticate, the error told you to run wrangler whoami, wrangler logout and wrangler login. It now names cf auth whoami, cf auth logout and cf auth login. When a Flagship binding without an id needed to run remotely, the error named Wrangler's app_id setting and suggested wrangler flagship apps create. It now names id and suggests cf flagship apps create.

    For the Vitest plugin, this applies to projects that load cloudflare.config.ts. Projects that use a Wrangler configuration file still see the Wrangler commands.

  • #16834 8e57331 Thanks @​edmundhung! - Fix test files never finishing when a socket read rejects after a Worker handler has answered

    Previously, if a handler finished while a socket was still being read, for example a database client's connection, the read's rejection could leave vitest run waiting forever after the tests passed. Vitest now reports the unhandled error and the run ends.

  • Updated dependencies [8b2a363, 5f539b5, dc47e6d, 575d136, 3626ee8]:

1.8.0

Minor Changes

  • #16682 5966749 Thanks @​ghostwriternr! - Run the Containers that cloudflare.config.ts attaches to Durable Objects

    Previously, projects that load cloudflare.config.ts through the config option ran those Durable Objects without their Containers. The plugin now prepares the Containers' images and runs them, as it does for Wrangler configuration files. Dockerfile and build context paths are relative to the directory that contains cloudflare.config.ts.

    cloudflare.config.ts has no setting that disables local Containers, so, as with the Vite plugin, projects with Container-backed Durable Objects need Docker to run their tests.

Patch Changes

  • #16824 877b249 Thanks @​jamesopstad! - Move streaming tail consumers to experimental.streamingTailConsumers in cloudflare.config.ts

    Streaming Tail Workers are now declared in a separate, experimental list instead of with streaming: true on a tailConsumers entry. tailConsumers now only lists Tail Workers with a tail() handler. This is a breaking change to the experimental config API: move each entry that set streaming: true to experimental.streamingTailConsumers, without the streaming field.

    export default defineConfig({
      worker: {
        tailConsumers: [{ worker: "tail-worker" }],
        experimental: {
          streamingTailConsumers: [{ worker: "streaming-tail-worker" }],
        },
      },
    });

    Fields under experimental may change or be removed without a major version bump. The wrangler-to-cf codemod now converts streaming_tail_consumers to experimental.streamingTailConsumers.

  • #16734 c47cca7 Thanks @​matingathani! - Fix CommonJS dependencies being loaded as ES modules under Vitest 5 inline projects

    A dependency with its own "type": "commonjs" package.json was treated as an ES module when an earlier .js file elsewhere in the project had been classified by the project's "type": "module" package.json. The dependency then failed at import with errors such as Cannot set properties of undefined or exports is not defined. The nearest package.json now always decides how a .js file is loaded.

... (truncated)

Commits
  • 1e688ba Version Packages (#16836)
  • 3626ee8 Remove CLOUDFLARE_CF_AUTH and require explicit auth for remote bindings ses...
  • 8e57331 [vitest-plugin] Fix test files hanging when a socket read rejects after a han...
  • cc238b2 Version Packages (#16814)
  • 877b249 Move streaming tail consumers to experimental.streamingTailConsumers in `cl...
  • c47cca7 [vitest-plugin] fix: let the nearest package.json decide a .js file's module ...
  • 5966749 [vitest-plugin] Support Container tests with cloudflare.config.ts (#16682)
  • 2674eef Version Packages (#16799)
  • d437be3 [vitest-plugin] Support Container tests (#15695)
  • bf3ec7b Version Packages (#16729)
  • Additional commits viewable in compare view

Dependabot compatibility score

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@cloudflare/vitest-plugin](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/vitest-plugin) from 1.4.11 to 1.8.1.
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/vitest-plugin/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/@cloudflare/vitest-plugin@1.8.1/packages/vitest-plugin)

---
updated-dependencies:
- dependency-name: "@cloudflare/vitest-plugin"
  dependency-version: 1.8.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

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 Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants