Next.js shifts default browser targets
Next.js has updated its default browser support to track the current baseline widely available Browserslist query. Because Next.js is one of the most widely used React frameworks, this change has outsized influence on which browsers developers are effectively building for. As updated Next.js instances roll forward, they will carry fewer polyfills and transforms, and developers working in those projects will be able to use a broader set of web platform features safely.
Baseline in action series grows
The Baseline in action series pairs articles with demos showing how to combine Baseline-supported features to build common UI components. Early topics cover container queries, image gallery construction, and <dialog> and popover. The series is expected to expand through the end of 2025 and into 2026; more detail is in the announcement.
New case studies on browser support strategy
Two Baseline case studies were published in November:
- How Cybozu eliminated browser compatibility overhead with Baseline
- How Target.com used Baseline to modernize features
Both stories look at how professional teams redefined browser support criteria. That process typically requires stakeholder buy-in because supporting fewer or different browsers is a consequential decision. The case studies illustrate how each organization used Baseline to make that call more tractable.
November Baseline updates
One feature became Baseline Newly available in November:
A larger set moved to Baseline Widely available:
color()color-mix()- Compression streams
- Lab and LCH
nth-child() of <selector>oklab()andoklch()- WebRTC SCTP information
If anything Baseline-related was missed in the November roundup, you can file an issue and it will be picked up in a future digest.
