@cloudflare/wrangler
Advanced tools
Changelog
v1.17.0
feat: capture panics and generate error report - nilslice, pull/1888
This PR adds support for wrangler error reporting. Currently, all panics are caught and a report is generated, then written to disk. wrangler report
or wrangler report --log <file-name.log>
will upload the corresponding error report to Cloudflare
fix: clarify error messages around durable objects beta - nilslice, pull/1921
Disambiguates error message described in #1859, adds more clarity around other places where Durable Object usage in beta may conflict with wrangler
functionality.
Fix filtering by extension for js assets - rubenamorim, pull/1722
Fixes #1719
fix: use latest cloudflare api client, resolving wrangler whoami issue - nilslice, pull/1920
Updates cloudflare-rs
crate to https://github.com/cloudflare/cloudflare-rs/commit/ae936d4b180155bafe5c44482a746fa490513df2, which should fix #1914.
Handle String panic payloads when generating reports - ObsidianMinor, pull/1934
Standard panics will only produce &str and String, but we were only handling &str, so this adds handling for String.
chore: tokio ecosystem update - nataliescottdavidson, pull/1886
Update tokio ecosystem crates including hyper, rustls, openssl and necessary API changes Rewrite get_tunnel_url to use tokio-retry
failure --> anyhow - caass, pull/1881
Follow up to #1880
Switch from deprecated failure
to anyhow
. read this
further reduce complexity of main - nilslice, pull/1937
In many ways, thanks to @ObsidianMinor's work on #1932, we can split up the cli code further and keep a simple main.rs
.
rebases & updates durable-objects-rc branch - nilslice, pull/1919
Reduce cognitive complexity in main - ObsidianMinor, pull/1932
This replaces our massive clap App with a much simpler Cli struct that has all the same information in an easier to understand and modify format (types).
Updated cloudflared download link - arunesh90, pull/1900
The commit included with this PR updates the download link for cloudflared, as the previous link is no longer current and is now a redirect to https://developers.cloudflare.com/cloudflare-one/connections/connect-apps
Upgrade to GitHub-native Dependabot - dependabot, pull/1887
Changelog
🍏 v1.16.1
Add wasm_modules
config field for bundling arbitrary WebAssembly modules. - losfair, pull/1803
Currently it seems that wrangler only supports WebAssembly modules included from a rust
or webpack
project.
This pull request enables the inclusion of arbitrary WebAssembly modules through a wasm_modules
config field.
fix: use x86_64 arch for pre-built downloads on M1 devices - nilslice, pull/1876
This PR forces the use of a pre-built x86_64 binary on a aarch64/arm64 Apple system. For M1 devices specifically, it will fix wrangler generate
, and wrangler build
for type = "rust"
wrangler projects.
There is another semi-related ... truncated
chore: include @cloudflare/binary-install directly as source - nilslice, pull/1877
This PR inlines the @cloudflare/binary-install
dependency as a quickfix for #1811, in which usage reports indicated that the module occasionally failed to install.
I tested this by running npm i && node run-wrangler.js
on both `npm
... truncated
Stop assuming KV values are UTF8 text - koeninger, pull/1878
Implementation of kv:key get is calling text() on the result of the api call, so it's replacing non-utf8 values with ef bf bd, the unicode REPLACEMENT CHAR. KV values can be arbitrary bytes, we shouldn't assume they're UTF8 text, so this p ... truncated
Changelog
1.16.0
Custom Builds and Modules - xortive, caass, pull/1855
Custom Builds and Modules has finally landed in a main release! There's too many new features to write about in a changelog, so here's a link to the docs.
add --format
option, including default json
and new pretty
- caass, pull/1851
You can now pass --format pretty
to wrangler tail
to get pretty printed logs!
--format json
is also available, and gives you the existing JSON-formatted logs.
Revert "Print line and column numbers for exception thrown (#1645)" - Electroid, pull/1835
This reverts commit 74a89f7c383bc22758cbe55096ce3016c5c319d7.
Closes #1826
This commit is causing wrangler dev
to not show uncaught exceptions. Reverting chrome-devtools-rs
was also necessary.
We have a fix in progress to fix the underlying issue and re-introduce line and column numbers.
Don't generate usage_model = ""
by default - xortive, issues/1850
Generating usage_model = ""
by default was violating the toml spec, which broke
wrangler init --site
as usage_model
came after [site]
.
Changelog
1.15.1
Add config option to switch usage model to unbound - ObsidianMinor, pull/1837
fix: remove unused import of WasmMainTemplatePlugin - jasikpark, pull/1802
This should improve #1721. https://github.com/cloudflare/wrangler-legacy/issues/1721#issuecomment-791974664
Hot fix for error message helper not working - Electroid, pull/1847
The JSON is pretty printed, which means it contains a space.
Revert "Print line and column numbers for exception thrown (#1645)" - Electroid, pull/1835
This reverts commit 74a89f7c383bc22758cbe55096ce3016c5c319d7.
Closes #1826
This commit is causing wrangler dev
to not show uncaught exceptions. Reverting chrome-devtools-rs
was also necessary.
Changelog
1.15.0
fix: remove unused import of WasmMainTemplatePlugin - jasikpark, pull/1802
This should improve #1721. https://github.com/cloudflare/wrangler-legacy/issues/1721#issuecomment-791974664
Revert pull/1748 - xortive, pull/1804
pull/1748 turned out to interact poorly with workers-sites projects, causing npm install
to not be run, breaking the build.
We're going to revert this change. Folks already depending on it should use custom builds (pull/1677) once it makes it into a release candidate.
We incremented the minor version number instead of making a patch release, as this change is more significant than a simple bugfix.
Changelog
1.14.1
revert default install location change - xortive, pull/1798
In 1.14.0, we changed the default install location from ~/.wrangler
to node_modules
,
to allow npx wrangler
to use the pinned version in a project's dependencies. It seems that
this is causing issues, so we're rolling it back in favor of having folks who want this behavior,
to specify a the install location in the config
section of package.json. We'll document this soon.