Skip to content

Add Wrangler v4 RC changelog entry #20355

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 13 commits into from
Feb 28, 2025
Merged

Add Wrangler v4 RC changelog entry #20355

Changes from 1 commit
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
6674519
Add v4 RC changelog entry
penalosa Feb 27, 2025
fb2ba5e
Apply suggestions from code review
penalosa Feb 27, 2025
3c5bea5
Copy and language updates
irvinebroque Feb 28, 2025
e6ebd21
More updates
irvinebroque Feb 28, 2025
dc892c4
Update 2025-02-27-wrangler-v4-rc.mdx
irvinebroque Feb 28, 2025
221cdcb
Apply suggestions from code review
irvinebroque Feb 28, 2025
419f9c6
Add more detail to deprecations
penalosa Feb 28, 2025
33ac357
Update src/content/changelog/workers/2025-02-27-wrangler-v4-rc.mdx
penalosa Feb 28, 2025
1f7e09a
Update src/content/changelog/workers/2025-02-27-wrangler-v4-rc.mdx
penalosa Feb 28, 2025
de7e3e8
Add current deprecations to v3 deprecations page
penalosa Feb 28, 2025
d231eb5
fix headers
penalosa Feb 28, 2025
d51acd0
undo format
penalosa Feb 28, 2025
93b911e
use today date
penalosa Feb 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
54 changes: 54 additions & 0 deletions src/content/changelog/workers/2025-02-27-wrangler-v4-rc.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,54 @@
---
title: Introducing Wrangler v4's release candidate
description: You can now try out the v4 RC for Wrangler by installing `[email protected]`
products:
- workers
date: 2025-02-27T11:00:00Z
---

import { PackageManagers } from "~/components";

TLDR: Try out the Wrangler v4 RC by installing via your favourite package manager:

<PackageManagers pkg="wrangler@v4-rc" />

Wrangler v3 was released in May 2023, and since then has seen amazing growth and usage—from just \~250,000 downloads a week back then to 1M+ now. It's time for the next chapter in Wrangler's journey: v4. This release will bring new features and unlock new possibilities for the developer platform, but for the vast majority of users you _won't need to make any changes to upgrade_. It'll be as simple as upgrading Wrangler.

We're working on a more detailed migration guide, but here's a brief list of the changes to expect:

#### Changes

- **Upgraded `esbuild` version**
This has been a highly-requested feature for a long time, and will allow you to use more modern JavaScript features in your Workers, including import attributes and `using` statements

- **`--local` by default for all commands**
All commands that access resources (e.g. `wrangler kv`, `wrangler r2`, `wrangler d1`) will now access local datastores by default

- **Updated Node.js support policy**
Wrangler will now support the active, maintenance, and current versions of Node.js (currently v18+)

- **Deprecated features removed**
All deprecated features have been removed from Wrangler, including
- Arguments:
Copy link
Contributor

@irvinebroque irvinebroque Feb 28, 2025

Choose a reason for hiding this comment

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

@lrapoport-cf @penalosa for the things below, I think if you work on Wrangler it's easy to look at this list and know "oh yeah these are all old things that there are other ways of doing" — but right now this comes across as a long list without guidance on what people can do instead.

Especially since we already have a lot of the deprecations and guidance here:

https://developers.cloudflare.com/workers/wrangler/deprecations/#wrangler-v3

...should we just update that page with the RC v4 stuff, and in this post, link directly to it?

I think it could help us tighten up the post, and also help send the reader to the page that will give them the relevant details they need

Copy link
Contributor Author

@penalosa penalosa Feb 28, 2025

Choose a reason for hiding this comment

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

I included the list for completeness, but we could actually remove a fair few—a lot of these were deprecated in v2 and have never worked in v2+

Copy link
Contributor

@irvinebroque irvinebroque Feb 28, 2025

Choose a reason for hiding this comment

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

strawman suggestion:

  • keep any deprecations that are new, that we haven't communicated previously
  • for the ones we have already talked about for v2 and v3, just say that things previously deprecated are now removed, and link to that deprecations page
  • update the deprecations page with this list we have here so that it's concrete somewhere in dev docs

Sound good?

Then we can follow up and make the deprecations page slightly clearer

Think that would go a long way and then we're good here to ship this

Copy link
Contributor Author

@penalosa penalosa Feb 28, 2025

Choose a reason for hiding this comment

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

Sounds good, although maybe we shouldn't update the deprecation page at this point? Once v4 is released properly we'll have a full migration guide we can point people to, but that's not fully ready yet.

Copy link
Contributor Author

@penalosa penalosa Feb 28, 2025

Choose a reason for hiding this comment

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

I don't feel strongly about it though—happy to update that now if you think that makes sense.

Copy link
Contributor Author

@penalosa penalosa Feb 28, 2025

Choose a reason for hiding this comment

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

I've made this more user-focused in https://github.com/cloudflare/cloudflare-docs/pull/20355/commits/419f9c6a25f8e05f5041e4495d353cbccaec256a—how does that look?

Copy link
Contributor

@lrapoport-cf lrapoport-cf Feb 28, 2025

Choose a reason for hiding this comment

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

i left a couple really small comments, but overall looks good to me! agree with @irvinebroque we should update the deprecations page, for completeness

- `wrangler dev/deploy --legacy-assets`
- `wrangler dev/deploy --format`
- Commands:
- `wrangler version`
- `wrangler publish`
- `wrangler generate`
- `wrangler config`
- `wrangler preview`
- `wrangler route`
- `wrangler subdomain`
- APIs
- `getBindingsProxy()`
- Config file properties
- `type`
- `webpack_config`
- `miniflare`
- `build.upload`
- `zone_id`
- `usage_model`
- `experimental_services`
- `kv-namespaces`
- `legacy_assets`