-
Notifications
You must be signed in to change notification settings - Fork 10k
adding changelog for Wrangler interactive improvement for Assets deployment #25012
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
yomna-shousha
merged 3 commits into
cloudflare:production
from
yomna-shousha:yomna/wrangler-assets-interactive
Sep 9, 2025
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
63 changes: 63 additions & 0 deletions
63
src/content/changelog/workers/2025-09-09-interactive-wrangler-assets.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,63 @@ | ||
| --- | ||
| title: Deploy static sites to Workers without a configuration file | ||
| description: Wrangler now guides you through deploying static assets with interactive prompts and automatic configuration generation when no wrangler.jsonc file exists. | ||
| products: | ||
| - workers | ||
| date: 2025-09-09 | ||
| --- | ||
|
|
||
| Deploying static site to Workers is now easier. When you run `wrangler deploy [directory]` or `wrangler deploy --assets [directory]` without an existing [configuration file](/workers/wrangler/configuration/), [Wrangler CLI](/workers/wrangler/) now guides you through the deployment process with interactive prompts. | ||
|
|
||
| ## Before and after | ||
|
|
||
| **Before:** Required remembering multiple flags and parameters | ||
| ```bash | ||
| wrangler deploy --assets ./dist --compatibility-date 2025-09-09 --name my-project | ||
| ``` | ||
|
|
||
| **After:** Simple directory deployment with guided setup | ||
| ```bash | ||
| wrangler deploy dist | ||
| # Interactive prompts handle the rest as shown in the example flow above | ||
| ``` | ||
|
|
||
| ## What's new | ||
|
|
||
| **Interactive prompts for missing configuration:** | ||
| - Wrangler detects when you're trying to deploy a directory of static assets | ||
| - Prompts you to confirm the deployment type | ||
| - Asks for a project name (with smart defaults) | ||
| - Automatically sets the compatibility date to today | ||
|
|
||
| **Automatic configuration generation:** | ||
| - Creates a `wrangler.jsonc` file with your deployment settings | ||
| - Stores your choices for future deployments | ||
| - Eliminates the need to remember complex command-line flags | ||
|
|
||
| ## Example workflow | ||
|
|
||
| ```bash | ||
| # Deploy your built static site | ||
| wrangler deploy dist | ||
|
|
||
| # Wrangler will prompt: | ||
| ✔ It looks like you are trying to deploy a directory of static assets only. Is this correct? … yes | ||
| ✔ What do you want to name your project? … my-astro-site | ||
|
|
||
| # Automatically generates a wrangler.jsonc file and adds it to your project: | ||
| { | ||
| "name": "my-astro-site", | ||
| "compatibility_date": "2025-09-09", | ||
| "assets": { | ||
| "directory": "dist" | ||
| } | ||
| } | ||
|
|
||
| # Next time you run wrangler deploy, this will use the configuration in your newly generated wrangler.jsonc file | ||
| wrangler deploy | ||
| ``` | ||
|
|
||
| ## Requirements | ||
|
|
||
| - You must use Wrangler version 4.24.4 or later in order to use this feature | ||
|
|
||
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.
Uh oh!
There was an error while loading. Please reload this page.