EAS CLI v21 rewrites onboarding while Nuxt 4.5 and SvelteKit 3 prepare for major transitions

EAS CLI v21 overhauls the developer onboarding experience

The biggest single release this week belongs to Expo's EAS CLI v21.0.0, which removes the eas onboarding command entirely and replaces it with a much more capable eas workflow:create flow. The new workflow command gains a --template flag, automatically configures EAS Build and EAS Update, installs the dev-client when needed, and generates shorter default file names like build.yml instead of eas-build.yml. For teams that have already grown past the onboarding phase, two follow-up patches add polish: EAS CLI v21.0.1 introduces eas project:delete for removing projects from the command line, along with an eas browse command that opens the project page on expo.dev, and EAS CLI v21.0.2 cleans up temporary working directories after eas build:inspect to prevent lingering disk usage from failed builds.

Nuxt 4.5 lays the groundwork for Nuxt 5

Nuxt 4.5 is the framework's most significant release in months, shipping three major build-layer upgrades: Vite 8, Rspack 2 powered by the new Rsbuild pipeline, and a stable error code system. The release also introduces experimental SSR streaming, a new useLayout composable, named views, and a nuxt/* build output contract with dev exports. Much of the work is invisible plumbing for Nuxt 5 — the team has moved core dependencies to unhead v3 and unctx v3, and switched the framework's own build to tsdown. The accompanying Nuxt 4.5 blog post walks through the highlights and migration notes. On the 3.x line, Nuxt v3.21.9 patches a Vite-node fallback issue and fixes CSS inlining for lazy components.

SvelteKit 3.0.0-next continues its breaking change streak

SvelteKit's pre-release cycle accelerated this week with four new 3.0.0-next versions. The most impactful change lands in @sveltejs/kit@3.0.0-next.9: the $lib alias is replaced with #lib, and the files.lib config option is removed. The same release makes handle's resolve always return a Promise, disallows cross-origin form submissions without a Content-Type header, and treats server-only directories (/server/ in paths) more strictly. @sveltejs/kit@3.0.0-next.10 moves defineEnvVars to @sveltejs/kit/env and skips import graph collection outside client environments for a performance win. @sveltejs/kit@3.0.0-next.11 introduces a major change: config exported from a universal route file now takes precedence over a server one, and special filename patterns have been made consistent. It also adds support for sourcemaps in production and function validators for environment variables. On the 2.x stable line, @sveltejs/kit@2.70.0 backports the defineEnvVars move, and @sveltejs/kit@2.69.3 fixes destructured load and actions export detection during type generation.

Next.js preview refines navigation and developer tools

Next.js v16.3.0-preview.6 enables fragment-based scroll by default, adds an experimental TypeScript CLI backend, and fixes navigation reversion with in-flight Server Actions. The canary line brought v16.3.0-canary.85 with fixes for Pages router 404 rendering and duplicate static files, v16.3.0-canary.86 adding a DevTools request panel for request insights, v16.3.0-canary.87 fixing metadata image caching with top-level await, and v16.3.0-canary.89 preventing Turbopack from server-rendering pages only reachable through soft navigation.

Svelte core adds performance fixes

The Svelte compiler itself received two patch releases: svelte@5.56.5 fixes derived reconnection logic and avoids unnecessary derived effects, while svelte@5.56.6 skips unnecessary blocker analysis for components without top-level await and reruns deriveds that had an abort controller on reconnection.