cloudflare/workers-sdk wrangler@0.0.14

on GitHub

Patch Changes

• #307 53c6318 Thanks @threepointone! - feat: wrangler secret * --local

  This PR implements wrangler secret for --local mode. The implementation is simply a no-op, since we don't want to actually write secret values to disk (I think?). I also got the messaging for remote mode right by copying from wrangler 1. Further, I added tests for all the wrangler secret commands.

• #324 b816333 Thanks @GregBrimble! - Fixes wrangler pages dev failing to start for just a folder of static assets (no functions)

• #317 d6ef61a Thanks @threepointone! - fix: restart the dev proxy server whenever it closes

  When we run wrangler dev, the session that we setup with the preview endpoint doesn't last forever, it dies after ignoring it for 5-15 minutes or so. The fix for this is to simply reconnect the server. So we use a state hook as a sigil, and add it to the dependency array of the effect that sets up the server, and simply change it every time the server closes.

  Fixes #197

  (In wrangler1, we used to restart the whole process, including uploading the worker again, making a new preview token, and so on. It looks like that they may not have been necessary.)

• #312 77aa324 Thanks @threepointone! - fix: remove --prefer-offline when running npm install

  We were using --prefer-offline when running npm install during wrangler init. The behaviour is odd, it doesn't seem to fetch from the remote when the cache isn't hit, which is not what I'm expecting. So we remove --prefer-offline.

• #311 a5537f1 Thanks @threepointone! - fix: custom builds should allow multiple commands

  We were running custom builds as a regular command with execa. This would fail whenever we tried to run compound commands like cargo install -q worker-build && worker-build --release (via #236). The fix is to use shell: true, so that the command is run in a shell and can thus use bash-y syntax like &&, and so on. I also switched to using execaCommand which splits a command string into parts correctly by itself.

• #321 5b64a59 Thanks @geelen! - fix: disable local persistence by default & add --experimental-enable-local-persistence flag

  BREAKING CHANGE:

  When running dev locally any data stored in KV, Durable Objects or the cache are no longer persisted between sessions by default.

  To turn this back on add the --experimental-enable-local-persistence at the command line.