-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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.
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
Changes from 2 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
6674519
Add v4 RC changelog entry
penalosa fb2ba5e
Apply suggestions from code review
penalosa 3c5bea5
Copy and language updates
irvinebroque e6ebd21
More updates
irvinebroque dc892c4
Update 2025-02-27-wrangler-v4-rc.mdx
irvinebroque 221cdcb
Apply suggestions from code review
irvinebroque 419f9c6
Add more detail to deprecations
penalosa 33ac357
Update src/content/changelog/workers/2025-02-27-wrangler-v4-rc.mdx
penalosa 1f7e09a
Update src/content/changelog/workers/2025-02-27-wrangler-v4-rc.mdx
penalosa de7e3e8
Add current deprecations to v3 deprecations page
penalosa d231eb5
fix headers
penalosa d51acd0
undo format
penalosa 93b911e
use today date
penalosa File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
54 changes: 54 additions & 0 deletions
54
src/content/changelog/workers/2025-02-27-wrangler-v4-rc.mdx
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,54 @@ | ||
| --- | ||
| title: Introducing Wrangler's v4 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. And for the vast majority of users, _no changes will be necessary to upgrade_—it'll be as simple as upgrading Wrangler. | ||
|
|
||
| We're working on a detailed migration guide that will accompany the v4 release. In the meantime, here's a brief list of the changes to expect: | ||
|
|
||
| #### Changes | ||
|
|
||
| - **Upgraded `esbuild` version** | ||
| A long-time highly-requested feature, this will now allow the use of more modern JavaScript features in Workers, including import attributes and `using` statements | ||
|
|
||
| - **`--local` by default for all commands** | ||
| All commands that access resources (for example, `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 will be removed from Wrangler, including | ||
| - Arguments: | ||
| - `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` | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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+
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
strawman suggestion:
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
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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