🏄♀️ 1.1.1
-
Features
-
Install current version, not latest - ashleygwilliams, issue/418
Previously the NPM installer for wrangler would always pull the most recent release from Github releases, and the installer did not increase version numbers when Wrangler did. Many users found this confusing. Now the installer will increment versions along with Wrangler releases, and point at specific versions rather than the most recent one at the time of installation.
-
Improve JSON errors debuggability - xtuc, pull/394
This PR improves JSON error output in
wrangler
. Specifically:-
If a
package.json
file fails to decode,wrangler
now emits a clearer error:$ wrangler build ⬇️ Installing wranglerjs... ⬇️ Installing wasm-pack... thread 'main' panicked at 'could not parse "./package.json": Error("expected `,` or `}`", line: 4, column: 3)', src/libcore/result.rs:999:5
-
If the
wranglerjs
backend returns invalid JSON, it now preserves the output file for further investigation. Note that the console doesn't print the output file location by default, and you will need to passRUST_LOG=info
while runningwrangler build
, and search for the--output-file=FILE
argument passed towranglerjs
:$ RUST_LOG=info wrangler build ⬇️ Installing wasm-pack... [2019-08-09T19:28:48Z INFO wrangler::commands::build::wranglerjs] Running "/Users/kristian/.nvm/versions/node/v12.1.0/bin/node" "/Users/kristian/src/workers/wrangler/wranglerjs" "--output-file=/var/folders/5x/yzqyqst11n518yl8xl7yv1f80000gp/T/.wranglerjs_output5eREv" # ...
-
If the preview service returns invalid JSON, it now emits a clearer error, and the full output can be seen by using
RUST_LOG=info
.Previously:
$ wrangler preview ⬇️ Installing wasm-pack... ⬇️ Installing wranglerjs... ✨ Built successfully. Error: Error("expected value", line: 2, column: 1)
Now:
$ wrangler preview ⬇️ Installing wranglerjs... ⬇️ Installing wasm-pack... ✨ Built successfully, built project size is 1 MiB. ⚠️ Your built project has grown past the 1MiB size limit and may fail to deploy. ⚠️ ✨ Error: https://cloudflareworkers.com/script: Server Error: 502 Bad Gateway
-
-
-
Fixes
-
Fix
wrangler config
for systems with non-unix EOL - xortive, issue/389wrangler config
was not properly truncating whitespace from the end of user input, resulting in a panic when trying to usewrangler publish
, becausewrangler
would try to create an HTTP header with invalid characters. Now,wrangler
will properly truncate extra whitespace (including\r
) from the end of the input intowrangler config
.
-
-
Maintenance
-
Migrate straggler emojis to terminal::emoji - EverlastingBugstopper, pull/382
This PR updates the last remaining instances where
wrangler
was using hard-coded emojis for messages, rather than usingterminal::emoji
. In addition, there are two instances where this PR changes the usage of the ⛔ emoji to⚠️ . -
Move test fixtures to their own directory - EverlastingBugstopper, pull/383
This PR aggregates fixtures used in integration tests into a
fixtures
directory to
make it easier to find/use them. -
Update issue templates to fit Github's data model - EverlastingBugstopper, pull/387
Our previous issue templates were not picked up by Github's user interface. This PR updates the templates to fit the accepted data model, and adds some style tweaks to make the templates easier to use.
-
Move Emoji formatting/messaging into new functions - ashleymichal, pull/391
This PR makes improvements to the internal messaging logic of Wrangler, allowing us to be more flexible in how we display information to users.
-
-
Documentation
-
Update README to include config, env var changes - ashleymichal, pull/379
In 1.1.0 we changed the
config
command to be interactive. This PR updates the README to reflect that change. -
Add section to readme about Vendored OpenSSL - xortive, pull/407
Wrangler has some external OpenSSL dependencies when installing on Linux -- this PR documents those dependencies, and how to install Wrangler using a vendored OpenSSL feature flag:
cargo install wrangler --features vendored-openssl
-