Next.js 14.2.31 represents an incremental update over version 14.2.30, primarily focusing on internal refinements and bug fixes rather than introducing major new features. Examining the package.json data reveals subtle differences in @next/env and @next/swc dependency versions, both incrementing from 14.2.30 to 14.2.31. This suggests targeted improvements within Next.js' environment handling and SWC (Speedy Web Compiler) integration, potentially enhancing build performance or compatibility.
While the majority of devDependencies remain consistent, these point updates are crucial for maintaining stability and optimal performance in Next.js applications. The 'releaseDate' confirms a more recent release. Developers should be aware of underlying improvements and ensuring they're running the latest version addresses potential issues.
The updated @next/swc version is particularly interesting for developers focused on build times, as SWC is a core component for compiling and transforming JavaScript/TypeScript code. Keeping this dependency up-to-date is part of the process of optimizing overall development workflow. The update also probably provides internal security improvements. Given the large number of dependencies in the package it is also possible that some dependencies were updated due to security reasons. These types of considerations can also drive developers to upgrade to the new version.
All the vulnerabilities related to the version 14.2.31 of the package
Next.js Improper Middleware Redirect Handling Leads to SSRF
A vulnerability in Next.js Middleware has been fixed in v14.2.32 and v15.4.7. The issue occurred when request headers were directly passed into NextResponse.next()
. In self-hosted applications, this could allow Server-Side Request Forgery (SSRF) if certain sensitive headers from the incoming request were reflected back into the response.
All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the next()
function.
More details at Vercel Changelog