Releases: cloudflare/workers-sdk
wrangler@3.111.0
Minor Changes
Patch Changes
create-cloudflare@2.39.0
Minor Changes
- #8264
1f3af77
Thanks @dcartertwo! - Create Cloudflare will no longer ask if the developer would like to use git if already in a git repository.
@cloudflare/vitest-pool-workers@0.7.4
@cloudflare/vite-plugin@0.1.7
Patch Changes
-
#8206
477f8d9
Thanks @jamesopstad! - Add support for binding to named entrypoints in the same worker -
#8266
9f05e8f
Thanks @jamesopstad! - Make it possible to overridebuilder.buildApp
in the user config or prior plugins -
Updated dependencies []:
- @cloudflare/unenv-preset@1.1.2
@cloudflare/pages-shared@0.13.10
wrangler@3.110.0
Minor Changes
- #8253
6dd1e23
Thanks @CarmenPopoviciu! - Add--cwd
global argument to thewrangler
CLI to allow changing the current working directory before running any command.
Patch Changes
miniflare@3.20250214.1
Patch Changes
-
#8247
a9a4c33
Thanks @GregBrimble! - feat: Omits Content-Type header for files of an unknown extension in Workers Assets -
#8239
6cae13a
Thanks @edmundhung! - fix: allow thefetchMock
option to be parsed upfront before passing it to Miniflare
create-cloudflare@2.38.2
Patch Changes
-
#8233
74a808f
Thanks @dependabot! - chore: update dependencies of "create-cloudflare" packageThe following dependency versions have been updated:
Dependency From To create-vue 3.14.0 3.14.2 -
#8241
708de7f
Thanks @dario-piotrowicz! - update experimental Next.js template to work on@opennextjs/cloudflare@0.5.x
-
#8240
47f56a2
Thanks @dario-piotrowicz! - fix: remove unnecessary flags passed tocreate-next-app
when creating Next.js apps in experimental modeThis change removes a set of flags that get passed to
create-next-app
that force the generated Next.js
application to have specific settings (e.g. typescript, tailwind, src directory, etc...) which are not
actually mandatory/recommended for the use of the open-next Cloudflare adapter -
#8215
eb0912d
Thanks @CarmenPopoviciu! - This change makes the user facing message C3 displays while waiting for DNS propagation, more friendly/informative. The idea is to inform users that DNS propagation might sometimes take even up to 2 minutes. This will hopefully prevent confusion around whether how long the process will take, or whether the process is stuck, etc. -
#8243
c62973b
Thanks @CarmenPopoviciu! - fix: Ensure we exit the process on "SIGINT" and "SIGTERM"Currently C3 does not explicitly exit the process if an error is thrown, or if a "SIGINT" or "SIGTERM" signal is received. This leads to situations when, if
ctrl+C
is pressed while there are still tasks in the stack/microtask queues (think in flight async xhr calls, or polling, or long running
while
loops), the current process will continue running until all those tasks are run to completion, and the queues are empty.This commit fixes this by explicitly calling
process.exit()
when an error is thrown (our internal "SIGINT"/"SIGTERM" handlers will throw aCancelError
), thus ensuring we always exit the process.
@cloudflare/workers-shared@0.14.4
Patch Changes
- #8247
a9a4c33
Thanks @GregBrimble! - feat: Omits Content-Type header for files of an unknown extension in Workers Assets