next.js

c8edeb6f - Remove clientParamParsing requirement from RDC for Navigations (#83661)

Remove clientParamParsing requirement from RDC for Navigations (#83661) ### What? Removes the temporary constraint that required `clientParamParsing` to be enabled for Resume Data Cache (RDC) for Navigations in PPR-enabled applications. ### Why? The upstream builder configuration issue that caused invalid query parameters to be passed to resume lambdas has been resolved. The `clientParamParsing` requirement was a temporary workaround that can now be safely removed. This enhancement allows more users on PPR to automatically benefit from RDC for RSC requests, improving performance by eliminating waterfalls when resuming prerendered pages without requiring additional feature flags. ### How? - Removed the `clientParamParsing` check from both build configuration and app-page template - Simplified the feature enablement logic for RDC in navigation scenarios The change affects two files: - `packages/next/src/build/index.ts`: Build-time configuration logic - `packages/next/src/build/templates/app-page.ts`: Runtime navigation support detection NAR-385