-
Features
-
BREAKING CHANGE: Require the
webpack_configfield inwrangler.tomlto build with a custom configuration - EverlastingBugstopper, issue/296 pull/847Wrangler will no longer use a
webpack.config.jsat the root of your project to build your worker. If you would like to continue using a custom build configuration, you will need to specify thewebpack_configfield in yourwrangler.tomllike so:name = "my-worker" workers_dev = true account_id = "01234567890987654321234567890" webpack_config = "webpack.config.js"
-
API Token Support - gabbifish/ashleymichal, issue/354 pull/471/pull/879
Wrangler can now be configured with API Tokens!
Don't worry, current configurations with an email address and a Global API Key will continue to work, but we highly recommend that you switch to API Tokens as they are a much more secure authentication method.
If you want to use API tokens, create an API token from the "Edit Cloudflare Workers" API token template here, and copy/paste it in the
wrangler configprompt. Alternatively, you can set theCF_API_TOKENenvironment variable. -
Add the ability to preview without opening the browser - EverlastingBugstopper, issue/256 pull/816
wrangler previewcan now be called with a--headlessflag that will not open the browser. -
Check for valid credentials when running
wrangler config- gabbifish, issue/439 pull/842Before this version of Wrangler,
wrangler configwould allow any input string to be passed for your user details. Now, Wrangler validates that the credentials will work with Cloudflare's API. -
Add a warning when publishing a Workers Site to a route without a trailing asterisk - EverlastingBugstopper, issue/814 pull/839
When publishing a Workers Site to your own domain, it's important that the Worker code runs on every path on your domain. This isn't particularly clear, so now when attempting to publish a Workers Site to a route without a trailing asterisk, Wrangler will print a warning message.
-
Better error message for publishing to a duplicate route - pradovic, issue/519 pull/813
When publishing to a route that is associated with another worker, Wrangler now prints a more actionable error message.
-
Better error message when webpack fails - ashleymichal, issue/428 pull/837
Wrangler now recommends running
npm installas a possible remedy for failed webpack builds.
-
-
Fixes
-
Properly handle errors when running Wrangler as a global npm package - jaredmcdonald, issue/848 pull/857
-
Clean up temporary build files - EverlastingBugstopper, pull/853
When building a script, Wrangler creates a temporary file. Old versions of Wrangler were quite messy about it, but now it cleans up after itself.
-
Fix the help text for
wrangler generate- EverlastingBugstopper, pull/830The default value for a template is now a complete and valid URL instead of a sample project name.
-
Remove --version on subcommands - EverlastingBugstopper, issue/791 pull/829
Each subcommand in Wrangler used to take a
--versionargument which would print the name of the subcommand. For instance,wrangler publish --versionwould printwrangler-publish. This wasn't super helpful, so we've removed that functionality. -
Fix a broken link in the README - victoriabernard92, pull/838
-
-
Maintenance
-
Create fixtures programatically - EverlastingBugstopper, pull/854
Wrangler's test suite relied on a large number of fixtures that it read in from the file system. Now, it writes the test fixtures itself and does not rely on reading fixtures from the file system.
-
Clean up Workers Sites logic - ashleymichal, issue/622 issue/643 pull/851
-
Call cloudflare-rs from https.rs - gabbifish, pull/841
We've refactored some of our API client code in order to make way for some future improvements.
-
Audit code comments - EverlastingBugstopper, pull/846
-
Update the author of the npm package - EverlastingBugstopper, pull/836
The author of the npm package is now wrangler@cloudflare.com
-
Remove unused code warnings when running tests - pradovic, issue/818 pull/832
Due to the way the Rust compiler works, some of our test code appeared to be unused, even though it wasn't really. After making a couple of modules public, there are no more warnings.
-
Use the same binding name for Rust and webpack wasm modules - ashleymichal, pull/822
-
Move the code for each subcommand to its own directory - EverlastingBugstopper, pull/831
-
Refactor upload forms - ashleymichal, pull/826
We've separated some tangled logic regarding the form Wrangler POSTs to the Cloudflare v4 API.
-
Pull npm version from package.json - EverlastingBugstopper, issue/812 pull/817
Wrangler's npm installer version now only needs updating in the package.json instead of both the package.json and the source code.
-
-
Documentation
-
Move Wrangler docs from READMEs to the Cloudflare Workers documentation site - victoriabernard92, pull/823
Wrangler has outgrown the README as primary documentation paradigm, and we've moved its documentation to the Cloudflare Workers documentation site.
-
Update the demo gif in the README - EverlastingBugstopper, issue/843 pull/868
The demo gif at the top of the README now accurately reflects the behavior of the latest Wrangler release.
-