fix(next/routing): apply only matching onMatch rules#90736
fix(next/routing): apply only matching onMatch rules#90736pieh wants to merge 2 commits intovercel:canaryfrom
Conversation
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
1 similar comment
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
# Conflicts: # packages/next-routing/src/resolve-routes.ts
Failing test suitesCommit: 8be3aac | About building and testing Next.js
Expand output● with maximumDiskCacheSize 85KB config › Production Mode Server support with next.config.js › should follow redirect from http to https when maximumRedirects > 0
Expand output● Telemetry CLI › production mode › emits event when swc fails to load
Expand output● nx-handling › should work for pages page ● nx-handling › should work for pages API ● nx-handling › should work with app page ● nx-handling › should work with app route |
Fix for
@next/routinglib to not applyonMatchrules on matches ifonMatchconditions are not met.Currently Adapters API output for immutable permanent
cache-controlheader is applied to all matches, not just/_next/staticones.This is trying to address point 3. from nextjs/adapters-wg#1 (other reports were already addressed in #89197)