chore: update dependencies #5
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chore(deps): update dependency wrangler to v4
…-monorepo chore(deps): update dependency vitest to v4
chore(deps): update dependency typescript to ^5.9.3
…itest-pool-workers-0.x chore(deps): update dependency @cloudflare/vitest-pool-workers to ^0.10.0
…-lockfile chore(deps): update dependency mimetext to v3.0.27
There was a problem hiding this comment.
Pull Request Overview
This PR upgrades dependencies and configuration settings for a Cloudflare Workers project, migrating to newer versions of wrangler (v3 → v4) and related tooling while updating the compatibility settings.
- Migrates from
node_compat = truetocompatibility_flags = ["nodejs_compat"]with updated compatibility date - Updates development dependencies including wrangler (v3→v4), vitest (v1→v3), TypeScript (v5.0→v5.9)
- Updates underlying runtime dependencies (miniflare, workerd, esbuild) to match wrangler v4 requirements
Reviewed Changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| wrangler.toml | Migrates compatibility configuration from deprecated node_compat flag to compatibility_flags with updated date |
| package.json | Updates dev dependencies to latest versions (wrangler v4, vitest v3, TypeScript v5.9) |
| package-lock.json | Reflects dependency updates with new/updated transitive dependencies |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…lags According to Cloudflare Workers documentation, compatibility_date should typically be specified before compatibility_flags for better readability and consistency with conventional patterns. Co-authored-by: Copilot <[email protected]>
…agement" This reverts commit 378e6e2.
aaccioly
force-pushed
the
chore-update-dependencies
branch
from
c4a4555 to
b96d715
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just updating the dependencies, as npm audit reported a few critical vulnerabilities.
By the way, Renovate can be quite handy here (it did most of the work for me). Otherwise, Dependabot is a good alternative.