cloudflare/workers-sdk create-cloudflare@2.38.2

on GitHub

Patch Changes

• #8233 74a808f Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The 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 to create-next-app when creating Next.js apps in experimental mode

  This 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 a CancelError), thus ensuring we always exit the process.