v0.0.53
What's Changed
New Features
- Added support for
nextConfig.instrumentationClientInjectconfiguration option - Pages Router now consumes
_next/dataJSON endpoint from the client, improving data fetching behavior
Bug Fixes
Security Fixes
- Fixed bodyParser configuration to be properly honored in Pages API routes
- Fixed
x-forwarded-protoheader handling in Edge API runtime whentrustProxyis disabled - Bounded cache key cardinality for
x-vinext-mounted-slotsto prevent potential issues - Kept draft mode secrets out of client-side defines to prevent exposure
App Router
- Fixed RSC navigation scroll targeting to align with Next.js behavior
- Fixed prerender parameter encoding to be properly preserved
- Fixed dynamic route parameter key ordering to match expected behavior
- Fixed history index preservation when external state writes occur
- Fixed metadata file exports for static App Router builds
- Fixed metadata streaming for non-HTML bot requests
- Fixed Edge runtime header application across all App Router response paths
- Fixed Vary header emission on Edge RSC route responses
- Fixed 307 status code preservation on document loads during prerender
- Fixed router.prefetch to properly throw errors on invalid URLs
- Fixed inline beforeInteractive script hoisting above resource hints
Pages Router
- Fixed basePath error route rendering when masked
- Fixed
revalidateReasonparameter passing togetStaticPropsand improved default Cache-Control headers - Fixed Promise-shaped
getServerSidePropsprops to be properly awaited - Fixed dangerous URI scheme detection to throw errors synchronously
- Fixed query string preservation in Link component and router.push calls
- Fixed default Cache-Control headers on
getServerSidePropsresponses - Fixed router push/replace methods to properly return Promise
- Fixed head element attributes to use
data-next-headinstead ofdata-vinext-head
Other Fixes
- Fixed 404 page default copy to match Next.js exactly
- Fixed image optimization to emit proper
/_next/imageURLs - Fixed server action redirects to properly resolve relative URLs
- Fixed Pages Router middleware redirect handling
- Fixed static file cache path normalization on Windows
- Fixed cache request data to be properly marked as private
- Fixed relative URL error handling in NextRequest to throw canonical errors
- Fixed font binding family preservation for local fonts
- Fixed stale build output cleanup before rebuilds
- Added warning when legacy middleware filename is detected
- Added warning for repeated forward slashes in Link href props
Contributors
@james-elicx
@NathanDrake2406
@Divkix
@jgeurts
@manNomi
@shulaoda
@ikxin