Expo tightens developer auth as Next.js settles its image pipeline

Expo draws the login line

The biggest headline this week comes from Expo, where Expo Go now requires authentication to run projects in development mode. As of the latest iOS app update, developers must be logged into both the Expo CLI in their terminal and the Expo Go app itself. Notably, Android and simulator versions are unaffected, and development builds themselves don't ask for credentials — only the in-app runner does. It's a friction point for the quick-testing loop, but it also signals how Expo is gating access to its hosted services as SDK 57 projects roll out.

Around that, EAS CLI got substantially more capable. EAS CLI v23.2.0 brings eas workflow:ssh <workflow-job-id> for opening SSH sessions on workflow job workers, plus a --tag flag to filter simulator sessions by app variant and real-time workflow run logs (replacing the previous 10-second polling). The v23.1.0 release earlier in the week made eas new prompt for an Expo SDK version with a --sdk-version flag, downloading templates from npm rather than GitHub so scaffolding matches the SDK you actually target. Taken together, EAS is getting more precise about versioning and debugging.

Next.js: image optimization returns, canary keeps refining

The quiet-but-important story is the AVIF fix. Next.js v16.3.4 re-enables AVIF Image Optimization after a regression, backporting fixes for infinite recursion in testmode passthrough fetch and a build error when aliasing TypeScript. The same regression is addressed in the maintaince line: Next.js v15.5.25 specifically re-enables AVIF optimization when newer versions of sharp are installed. For teams pinned to v15, that's a meaningful unblock.

Meanwhile canary marches toward v16.4 with incremental polish. Canary.17 turns adapter route collapses on by default and suppresses missing-package-manager errors in next info. Canary.16 routes server errors back to the client for unrecognized Server Actions — replacing silent failures with clear errors — while also upgrading web-vitals to v6. Canary.15 shrinks Turbopack cache size through per-family compression and removes a worker thread, and canary.14 removes Edge runtime handling from use-cache-wrapper, reflecting Next.js 16's broader move off Edge runtime. Even the smaller fixes matter: canary.18 corrects the source field in Turbopack CSS sourcemaps and adds docs for skipProxyUrlNormalize and skipTrailingSlashRedirect, while canary.19 fixes route info segment overrides not updating in the dev overlay. There's no single spotlight here, just steady erosion of rough edges.

Svelte preps 3.0

Over in Svelte-land, the September monthly roundup lands with Svelte 5.57 introducing getOrInsert and getOrInsertComputed on SvelteMap, and SvelteKit 3 officially reaching Release Candidate status. The sv CLI also swaps its old mcp add-on for a new ai-tools one and ships a task-based sveltekit-3 migration in sv@next. For anyone planning a SvelteKit upgrade, the RC and migration tooling are the signals to start testing.