cloudflare/workers-sdk @cloudflare/autoconfig@0.9.0 on GitHub

#16366 d174de8 Thanks @MattieTK! - Add an outputDir option to getDetailsForAutoConfig
Callers that already know which directory holds their built static assets can pass it as outputDir instead of having autoconfig detect one. Relative paths are resolved against the project path. This selects static-asset configuration for unconfigured projects even when framework dependencies are present, without running framework migrations or builds that could replace the requested assets. Existing Workers and Pages configurations, including deployments configured through the Cloudflare Vite plugin alone, retain their usual detection behavior.
Checking whether a Vite project already uses the Cloudflare plugin no longer writes the Vite config back to disk, preserving its line endings and trailing newline.

#16635 76e18a8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-01
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16537 a2d1338 Thanks @edmundhung! - Support React Router on cf from version 8.5.1
React Router 8.5.1 builds into the output directories that the Cloudflare Vite plugin v2 uses, which cf needs. Autoconfig now requires React Router 8.5.1 or later when configuring a project for cf, and stops with a clear message on earlier versions instead of letting cf build fail later. Projects configured for Wrangler keep the existing minimum of React Router 7.0.0.
#16588 3f14c76 Thanks @irvinebroque! - Run the project-local Vite+ executable for Vite+ projects
Use vp dev and vp build when Vite+ is declared. Its Vite alias does not expose a vite executable, so invoking vite can fail with pnpm or cause npm to fetch a separate Vite. Preserve framework-owned commands and custom scripts.
Updated dependencies [91f0e03, 76e18a8]:
- @cloudflare/config@0.29.1
- @cloudflare/workers-utils@0.50.2
- @cloudflare/cli-shared-helpers@0.3.1