1. 16 Jul, 2025 33 commits
  2. 15 Jul, 2025 7 commits
    • Zack Tanner's avatar
      upgrade to path-to-regexp@6.3.0 (#80123) · 7bcef687
      Zack Tanner authored
      Upgrades `path-to-regexp` to address backing concerns from
      `CVE-2024-45296`. As a result, this requires some additional
      pre-processing on the paths we generate for interception routes, to
      ensure we pass a compliant value into `path-to-regexp`.
      7bcef687
    • JJ Kasper's avatar
      Update NextAdapter type and re-export (#81692) · 8b7f4c50
      JJ Kasper authored
      Just fixes up the type and re-exports it so it can be imported directly
      from `next`. Also fixes test file not being type checked which didn't
      catch missing optional fields.
      8b7f4c50
    • Wyatt Johnson's avatar
      feat(build): optimize filterUniqueParamsCombinations to generate sub-combinations (#81321) · d884398d
      Wyatt Johnson authored
      ### What?
      
      Optimizes the `generateParamPrefixCombinations` function (previously
      `filterUniqueRootParamsCombinations`) to generate all unique
      sub-combinations of route parameters while ensuring partial shells
      include complete sets of root parameters.
      
      ### Why?
      
      The previous implementation only generated combinations at the root
      parameter level, which was insufficient for PPR (Partial Prerendering)
      shells. PPR needs all possible prefix combinations of route parameters
      to create effective shells for nested routes. For example, for a route
      `/[lang]/[region]/[slug]`, we need shells for:
      - `/[lang]/[region]` (complete root params)
      - `/[lang]/[region]/[slug]` (full route)
      
      Without proper sub-combinations, nested routes couldn't benefit from PPR
      shell optimization, leading to performance degradation.
      
      ### How?
      
      - Renamed `filterUniqueRootParamsCombinations` to
      `generateParamPrefixCombinations` to better reflect its expanded
      functionality
      - Added logic to generate all prefix combinations of route parameters,
      not just root-level combinations
      - Implemented root parameter validation to ensure partial shells only
      include complete sets of root parameters
      - Added comprehensive test coverage for edge cases including undefined
      parameters, missing keys, and parameter collisions
      - Optimized the algorithm to skip invalid combinations early when root
      parameters are incomplete
      
      The function now generates prefix combinations systematically while
      maintaining backward compatibility and preventing invalid partial
      routes.
      
      NAR-159
      
      ---------
      Co-authored-by: 's avatarHendrik Liebau <mail@hendrik-liebau.de>
      d884398d
    • Steven's avatar
      feat(next/image): warn when `images.qualities` is undefined (#81690) · 2b3728f9
      Steven authored
      Add a warning to Next.js 15.5 to prepare for Next.js 16 when
      `images.qualities` is undefined and the user attempted to use set
      `quality` prop to something other than 75.
      2b3728f9
    • nextjs-bot's avatar
      v15.4.2-canary.1 · 8b3c9337
      nextjs-bot authored
      8b3c9337
    • Benjamin Woodruff's avatar
      Turbopack: Generalize `ImportedBinding` effect creation to avoid as much… · 43b4364f
      Benjamin Woodruff authored
      Turbopack: Generalize `ImportedBinding` effect creation to avoid as much special-casing of SimpleAssignTarget (#81653)
      
      There was some logic here that checked for the existence of `SimpleAssignTarget`, and using that to bail out of `visit_ident`. That doesn't scale well to pattern assignments, but it turns out that we don't need to bail out, we just need to fix the codegen.
      
      Without this, https://github.com/vercel/next.js/pull/81654 breaks the test cases.
      43b4364f
    • Stojan Dimitrovski's avatar
      chore: Update `with-supabase` example to use `getClaims()` (#81383) · 8659d47c
      Stojan Dimitrovski authored
      Updates the `with-supabase` example to use the new and much faster (when
      project is configured with asymmetric JWT support)
      `supabase.auth.getClaims()` function instead of `getUser()`.
      
      ---------
      Co-authored-by: 's avatarBenjamin Woodruff <benjamin.woodruff@vercel.com>
      8659d47c