build(cli): TRAC-668 bump wrangler to 4.90.0#3010
Conversation
wrangler@4.24.3 produces a broken bundle for Next.js 16.2.x: the app-page-turbo.runtime.prod.js webpack runtime fails to initialize at request time with "Cannot read properties of undefined (reading 'require')". wrangler@4.90.0 bundles it correctly. Refs TRAC-668 Co-Authored-By: Claude <noreply@anthropic.com>
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Bundle Size ReportComparing against baseline from No bundle size changes detected. |
|
Verified this works with https://catalyst.catalyst-sandbox.store/ Required a |
wrangler@4.24.3 produces a broken bundle for Next.js 16.2.x: the app-page-turbo.runtime.prod.js webpack runtime fails to initialize at request time with "Cannot read properties of undefined (reading 'require')". wrangler@4.90.0 bundles it correctly. Refs TRAC-668 Co-authored-by: Claude <noreply@anthropic.com>
3 participants
Jira: TRAC-668
What/Why?
wrangler@4.24.3produces a broken worker bundle for Next.js 16.2.x: the webpack runtime insideapp-page-turbo.runtime.prod.jsfails to initialize at request time with "Cannot read properties of undefined (reading 'require')", returning 500 on every page.wrangler@4.90.0bundles it correctly.This unblocks the Next.js 16.2.x security patches (TRAC-668) from working on native hosting. Once this lands and a new alpha ships, the native-hosting workflow can drop its manual re-bundle workaround.
Testing
Build a Next.js 16.2.x app with
catalyst buildand confirm pages return 200. The existing native-hosting workflow onTRAC-668/security-bump-nextjs-reactvalidates this end-to-end.Migration
No migration required.
Refs TRAC-668