The Wire · Showcase
EVE SHIPS MOUNTED EXTENSIONS, NEXT.JS TACKLES TYPESCRIPT 7
By RepoJournal · Filed · About Vercel
Eve's extension system just went from concept to production-ready, while Next.js adds an experimental TypeScript CLI backend to sidestep the JS API bottleneck until TypeScript 7 lands officially.
Eve landed mounted extensions [1], a game-changer for agent customization: author an extension as a package with tools, connections, skills, and hooks, mount it with one line under `agent/extensions/`, and the build automatically composes it into the agent under a namespace. This is the modular architecture teams have been waiting for. In parallel, Eve fixed two critical dev-mode failures: remote URL query parameters now preserve correctly [2], and deployment protection challenges (both SSO redirects and structured 401 responses) now trigger auth recovery [3]. Eve also hardened frontmatter parsing against code injection and pinned OpenAPI connections to HTTPS [4]. Over in Next.js, the TypeScript 7 support PR [5] adds `experimental.useTypeScriptCli` so projects can run their local `tsc` during build without waiting for the legacy JavaScript API to catch up. Turbopack meanwhile is maturing service worker support: it now compiles service workers from pages router [6] and outputs them to `/_next/static/` [7] for Vercel deployment compatibility. The vercel-py SDK shipped a major upgrade [8]: Celery and Kombu can now use Vercel Queues as a backend via the new `vercel-celery` package. Supporting infrastructure landed too: header context helpers [9] make it safe to spawn threads with proper OIDC context, and workflow namespacing [10] solves multi-entrypoint conflicts. Workflow telemetry improved with client-side stream latency spans [11] and STSO step progress tracking [12].
One email a day. Unsubscribe in one click.
Keep up with Vercel in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Test mounted extensions in Eve against your custom agent packages vercel/eve [plan]
- → If TypeScript 7 is blocking your project, test experimental.useTypeScriptCli and report issues vercel/next.js [plan]
- → macOS CI users: upgrade setup-turborepo-remote-cache-action to fix bash 3.2 failures vercel/setup-turborepo-remote-cache-action [immediate]
- → Evaluate vercel-celery for Celery/Kombu workloads on Vercel Queues vercel/vercel-py [monitor]
References
- [1] feat(eve): mounted extensions ↗ vercel/eve
- [2] fix(eve): dev client - preserve remote URL query parameters ↗ vercel/eve
- [3] fix(eve): dev auth - recover Vercel protection challenges ↗ vercel/eve
- [4] fix(eve): safe-by-default frontmatter parsing and https-pinned OpenAPI connections ↗ vercel/eve
- [5] (TypeScript 7 Support) Add experimental TypeScript CLI backend ↗ vercel/next.js
- [6] [turbopack] Compile service workers registered from pages router pages ↗ vercel/next.js
- [7] [turbopack] Output service workers to `/_next/static/` ↗ vercel/next.js
- [8] Add `vercel-celery` -- Vercel Queues backend for Kombu and Runtime Cache storage backend for Celery ↗ vercel/vercel-py
- [9] vercel-headers: Add helpers to run threads/callabacks with header context ↗ vercel/vercel-py
- [10] [workflows sdk] support namespacing workflows ↗ vercel/vercel-py
- [11] feat(world-vercel): client-observed stream write/read e2e latency spans ↗ vercel/workflow
- [12] Report STSO step progress telemetry ↗ vercel/workflow