#454786c81ff0 Thanks @mrbbot! - fix: listen on IPv4 loopback only by default on Windows
Due to a known issue, workerd will only listen on the IPv4 loopback address 127.0.0.1 when it's asked to listen on localhost. On Node.js > 17, localhost will resolve to the IPv6 loopback address, meaning requests to workerd would fail. This change switches to using the IPv4 loopback address throughout Wrangler on Windows, while workerd#1408 gets fixed.
#453529df8e17 Thanks @mrbbot! - Reintroduces some internal refactorings of wrangler dev servers (including wrangler dev, wrangler dev --remote, and unstable_dev()).
These changes were released in 3.13.0 and reverted in 3.13.1 -- we believe the changes are now more stable and ready for release again.
There are no changes required for developers to opt-in. Improvements include:
fewer 'address in use' errors upon reloads
upon config/source file changes, requests are buffered to guarantee the response is from the new version of the Worker
Patch Changes
#45216c5bc704 Thanks @zebp! - fix: init from dash specifying explicit usage model in wrangler.toml for standard users
#455063708a94 Thanks @mrbbot! - fix: validate Host and Orgin headers where appropriate
Host and Origin headers are now checked when connecting to the inspector and Miniflare's magic proxy. If these don't match what's expected, the request will fail.
#4532311ffbd5 Thanks @mrbbot! - fix: change wrangler (pages) dev to listen on localhost by default
Previously, Wrangler listened on all interfaces (*) by default. This change switches wrangler (pages) dev to just listen on local interfaces. Whilst this is technically a breaking change, we've decided the security benefits outweigh the potential disruption caused. If you need to access your dev server from another device on your network, you can use wrangler (pages) dev --ip * to restore the previous behaviour.
#4474382ef8f5 Thanks @mrbbot! - fix: open browser to correct url pressing b in --remote mode
This change ensures Wrangler doesn't try to open http://* when * is used as the dev server's hostname. Instead, Wrangler will now open http://127.0.0.1.
#44883bd57238 Thanks @RamIdeas! - Changes the default directory for log files to workaround frameworks that are watching the entire .wrangler directory in the project root for changes
#454786c81ff0 Thanks @mrbbot! - fix: listen on IPv4 loopback only by default on Windows
Due to a known issue, workerd will only listen on the IPv4 loopback address 127.0.0.1 when it's asked to listen on localhost. On Node.js > 17, localhost will resolve to the IPv6 loopback address, meaning requests to workerd would fail. This change switches to using the IPv4 loopback address throughout Wrangler on Windows, while workerd#1408 gets fixed.
#453529df8e17 Thanks @mrbbot! - Reintroduces some internal refactorings of wrangler dev servers (including wrangler dev, wrangler dev --remote, and unstable_dev()).
These changes were released in 3.13.0 and reverted in 3.13.1 -- we believe the changes are now more stable and ready for release again.
There are no changes required for developers to opt-in. Improvements include:
fewer 'address in use' errors upon reloads
upon config/source file changes, requests are buffered to guarantee the response is from the new version of the Worker
Patch Changes
#45216c5bc704 Thanks @zebp! - fix: init from dash specifying explicit usage model in wrangler.toml for standard users
#455063708a94 Thanks @mrbbot! - fix: validate Host and Orgin headers where appropriate
Host and Origin headers are now checked when connecting to the inspector and Miniflare's magic proxy. If these don't match what's expected, the request will fail.
#4532311ffbd5 Thanks @mrbbot! - fix: change wrangler (pages) dev to listen on localhost by default
Previously, Wrangler listened on all interfaces (*) by default. This change switches wrangler (pages) dev to just listen on local interfaces. Whilst this is technically a breaking change, we've decided the security benefits outweigh the potential disruption caused. If you need to access your dev server from another device on your network, you can use wrangler (pages) dev --ip * to restore the previous behaviour.
#4474382ef8f5 Thanks @mrbbot! - fix: open browser to correct url pressing b in --remote mode
This change ensures Wrangler doesn't try to open http://* when * is used as the dev server's hostname. Instead, Wrangler will now open http://127.0.0.1.
#44883bd57238 Thanks @RamIdeas! - Changes the default directory for log files to workaround frameworks that are watching the entire .wrangler directory in the project root for changes
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/stevenson-space/shs/network/alerts).
Bumps wrangler from 3.1.1 to 3.19.0.
Release notes
Sourced from wrangler's releases.
... (truncated)
Changelog
Sourced from wrangler's changelog.
... (truncated)
Commits
5e67ea1Version Packages (#4536)63708a9fix: validateHost/Originheaders in magic proxy and `InspectorProxyWorke...86c81fffix: listen on IPv4 loopback only by default on Windows (#4547)6c5bc70fix: init from dash using explicit usage model for standard accounts (#4521)29df8e1Revert "Revert "startDevWorker - Milestone 1 (#4497)" (#4531)" (#4535)97727deVersion Packages (#4495)311ffbd[wrangler] fix: changewrangler (pages) devto listen onlocalhostby def...310281aRevert "startDevWorker - Milestone 1 (#4497)" (#4531)01eda78startDevWorker - Milestone 1 (#4497)961c8earemove unused npx-import dependency (#4477)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show