Skip to content

[email protected]

Latest
Latest
Compare
Choose a tag to compare
@workers-devprod workers-devprod released this 24 Jul 12:59
· 13 commits to main since this release
[email protected]
e424eb4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Minor Changes

  • #10016 c5b291d Thanks @emily-shen! - Interactively handle wrangler deploys that are probably assets-only, where there is no config file and flags are incorrect or missing.

    For example:

    npx wrangler deploy ./public will now ask if you meant to deploy a folder of assets only, ask for a name, set the compat date and then ask whether to write your choices out to wrangler.json for subsequent deployments.

    npx wrangler deploy --assets=./public will now ask for a name, set the compat date and then ask whether to write your choices out to wrangler.json for subsequent deployments.

    In non-interactive contexts, Wrangler will error as it currently does.

  • #9971 19794bf Thanks @edmundhung! - Improved script source display on the pretty error screen

Patch Changes

  • #9800 3d4f946 Thanks @helloimalastair! - remove banner from r2 getobject in pipe mode

  • #9910 7245101 Thanks @dario-piotrowicz! - make sure that the ready-on message is printed after the appropriate runtime controller is ready

    fix the fact that when starting a local (or remote) dev session the log saying Ready on http://localhost:xxxx could be displayed before the runtime is actually ready to handle requests (this is quite noticeable when locally running dev sessions with containers, where the ready message currently gets displayed before the container images building/pulling process)

  • #10031 823cba8 Thanks @vicb! - wrangler and vite-plugin now depend upon the latest version of unenv-preset

  • #10032 154acf7 Thanks @dario-piotrowicz! - add support for containers in wrangler multiworker dev

    currently when running wrangler dev with different workers (meaning that the -c|--config flag is used multiple times) containers are not being included, meaning that trying to interact with them at runtime would not work and cause errors instead. The changes here address the above making wrangler correctly detect and wire up the containers.

  • #9988 7fb0bfd Thanks @penalosa! - Correctly label mtls remote bindings warning

  • Updated dependencies [823cba8, 19794bf, 059a39e]:

Assets 2
Loading