Bump the development-dependencies group in /report-uri with 3 updates

[dependabot]

Bumps the development-dependencies group in /report-uri with 3 updates: @cloudflare/workers-types, prettier and wrangler.

Updates @cloudflare/workers-types from 4.20230904.0 to 4.20231025.0

Commits

• See full diff in compare view

Updates prettier from 3.0.3 to 3.1.0

Release notes

Sourced from prettier's releases.

3.1.0

diff

🔗 Release note

Changelog

Sourced from prettier's changelog.

3.1.0

diff

🔗 Release Notes

Commits

• e8ac9f8 Release 3.1.0
• 6a1d409 chore(deps): update dependency eslint-plugin-regexp to v2 (#15521)
• f4d93d3 chore(deps): update dependency esbuild to v0.19.5 (#15630)
• 4fc71a5 chore(deps): update dependency flow-parser to v0.221.0 (#15637)
• d452f45 chore(deps): update dependency eslint-plugin-jest to v27.6.0 (#15635)
• eb84a60 chore(deps): update dependency @​types/estree to v1.0.5 (#15625)
• 2af23ee chore(deps): update dependency webpack to v5.89.0 (#15640)
• 8f27c73 chore(deps): update dependency eslint-plugin-unicorn to v49 (#15642)
• cdc5f5a chore(deps): update dependency webpack to v5.89.0 (#15639)
• 14607ef chore(deps): update dependency eslint-plugin-n to v16.3.1 (#15636)
• Additional commits viewable in compare view

Updates wrangler from 3.7.0 to 3.15.0

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

• #4201 0cac2c46 Thanks @​penalosa! - Callout --minify when script size is too large

• #4209 24d1c5cf Thanks @​mrbbot! - fix: suppress compatibility date fallback warnings if no wrangler update is available

  If a compatibility date greater than the installed version of workerd was configured, a warning would be logged. This warning was only actionable if a new version of wrangler was available. The intent here was to warn if a user set a new compatibility date, but forgot to update wrangler meaning changes enabled by the new date wouldn't take effect. This change hides the warning if no update is available.

  It also changes the default compatibility date for wrangler dev sessions without a configured compatibility date to the installed version of workerd. This previously defaulted to the current date, which may have been unsupported by the installed runtime.

• #4135 53218261 Thanks @​Cherry! - feat: resolve npm exports for file imports

  Previously, when using wasm (or other static files) from an npm package, you would have to import the file like so:

  import wasm from "../../node_modules/svg2png-wasm/svg2png_wasm_bg.wasm";

  This update now allows you to import the file like so, assuming it's exposed and available in the package's exports field:

  import wasm from "svg2png-wasm/svg2png_wasm_bg.wasm";

  This will look at the package's exports field in package.json and resolve the file using resolve.exports.

• #4232 69b43030 Thanks @​romeupalos! - fix: use zone_name to determine a zone when the pattern is a custom hostname

  In Cloudflare for SaaS, custom hostnames of third party domain owners can be used in Cloudflare. Workers are allowed to intercept these requests based on the routes configuration. Before this change, the same logic used by wrangler dev was used in wrangler deploy, which caused wrangler to fail with:

  ✘ [ERROR] Could not find zone for [partner-saas-domain.com]

• #4198 b404ab70 Thanks @​penalosa! - When uploading additional modules with your worker, Wrangler will now report the (uncompressed) size of each individual module, as well as the aggregate size of your Worker

Patch Changes

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.15.0

Minor Changes

• #4201 0cac2c46 Thanks @​penalosa! - Callout --minify when script size is too large

• #4209 24d1c5cf Thanks @​mrbbot! - fix: suppress compatibility date fallback warnings if no wrangler update is available

  If a compatibility date greater than the installed version of workerd was configured, a warning would be logged. This warning was only actionable if a new version of wrangler was available. The intent here was to warn if a user set a new compatibility date, but forgot to update wrangler meaning changes enabled by the new date wouldn't take effect. This change hides the warning if no update is available.

  It also changes the default compatibility date for wrangler dev sessions without a configured compatibility date to the installed version of workerd. This previously defaulted to the current date, which may have been unsupported by the installed runtime.

• #4135 53218261 Thanks @​Cherry! - feat: resolve npm exports for file imports

  Previously, when using wasm (or other static files) from an npm package, you would have to import the file like so:

  import wasm from "../../node_modules/svg2png-wasm/svg2png_wasm_bg.wasm";

  This update now allows you to import the file like so, assuming it's exposed and available in the package's exports field:

  import wasm from "svg2png-wasm/svg2png_wasm_bg.wasm";

  This will look at the package's exports field in package.json and resolve the file using resolve.exports.

• #4232 69b43030 Thanks @​romeupalos! - fix: use zone_name to determine a zone when the pattern is a custom hostname

  In Cloudflare for SaaS, custom hostnames of third party domain owners can be used in Cloudflare. Workers are allowed to intercept these requests based on the routes configuration. Before this change, the same logic used by wrangler dev was used in wrangler deploy, which caused wrangler to fail with:

  ✘ [ERROR] Could not find zone for [partner-saas-domain.com]

• #4198 b404ab70 Thanks @​penalosa! - When uploading additional modules with your worker, Wrangler will now report the (uncompressed) size of each individual module, as well as the aggregate size of your Worker

Patch Changes

• #4215 950bc401 Thanks @​RamIdeas! - fix various logging of shell commands to correctly quote args when needed

... (truncated)

Commits

• a027b57 Version Packages (#4245)
• 3d55f96 fix: store temporary files in .wrangler (#4127)
• be0c628 Bump miniflare version to 20231023 (#4274)
• b404ab7 Log size of additional modules (#4198)
• 69b4303 Use zone_name for deployment of custom hostnames (#4232)
• 24d1c5c [wrangler] Clean up compatibility fallback warnings (#4209)
• 5321826 feat: support npm resolution for file imports (#4135)
• 775fb07 Disconnect parent process IPC channel when child process disconnects (#4267)
• 0cac2c4 Callout --minify when script size is too large (#4201)
• 0579803 Wrangler and C3: Move the cli folder of C3 into @​cloudflare/cli and make Wran...
• Additional commits viewable in compare view

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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Superseded by #162.