create-cloudflare@2.70.14
Patch Changes
-
#14505
65b0ccfThanks @petebacondarwin! - Stop pre-approvingsharp's build script in generated projectsminiflare0.35+ shipssharp0.35, which no longer has aninstalllifecycle script, so generatedpnpm-workspace.yamlfiles no longer pre-approvesharpunderallowBuilds.esbuildandworkerdare still pre-approved because they retain their install/postinstallscripts. -
#14761
c64cad3Thanks @dependabot! - Update dependencies of "create-cloudflare"The following dependency versions have been updated:
Dependency From To nuxi 3.36.1 3.37.0 -
#14789
67f55b7Thanks @dependabot! - Update dependencies of "create-cloudflare"The following dependency versions have been updated:
Dependency From To create-vike 0.0.662 0.0.664 -
#14613
620227dThanks @lucasmzz! - Fix Cloudflare bindings being unavailable duringnuxt devin pnpm projects created from the Nuxt templateThe Nuxt (Workers) template explicitly installs
h3when using pnpm, so that theH3EventContexttype augmentation inenv.d.tscan resolve theh3module under pnpm's isolatednode_moduleslayout. Since h3'slatestnpm dist-tag moved to the 2.x release candidates, this installedh3@2.0.1-rc.xalongside theh3@1.xthat Nuxt/Nitro run on. Nitro's auto-import layer then resolvedgetRequestURLfrom h3 v2, which throws when called with an h3 v1 event inside thenitro-cloudflare-devrequest hook. Nitro swallows request-hook errors, so the hook silently failed before assigningevent.context.cloudflare, and any server route accessing bindings crashed with "Cannot read properties of undefined (reading 'env')".The template now installs
h3@^1, matching the h3 major that nitropack depends on. -
#14769
d059704Thanks @edmundhung! - Stop adding a custom React Router server entry file to new projectsReact Router 8.2 now provides a Web Streams-compatible default server entry for non-Node runtimes. Newly generated Cloudflare projects use that default and only need
app/entry.server.tsxfor custom server rendering.