JJ Kasper

This commit **enhances the documentation** for **CDN caching** by adding a crucial clarification to the `cdn-caching.mdx` guide. It introduces a "Good to know" note advising users that if a proxy or middleware runs behind a CDN cache, **middleware-dependent requests should bypass the cache**. This **documentation improvement** ensures that the middleware or proxy remains the authoritative source of truth for dynamic content, preventing potential issues with stale data. The update provides **critical guidance** for configuring robust caching strategies in complex application architectures.

This commit **relaxes the condition** for uploading adapter test results within the **CI/CD pipeline**, specifically in the `test_e2e_deploy_release.yml` workflow. It modifies the `upload-adapter-test-results` step to run when the effective Next version value does not start with `http`, allowing `canary` and release tags to trigger the upload. This **maintenance update** addresses an issue where valid canary release runs, using a commit SHA as `target_commitish`, were incorrectly skipping the upload. The change ensures that **canary and release tag builds** consistently upload their adapter test results, improving test reporting for critical releases.

This commit significantly **refactors and expands the documentation for Next.js deployment adapters**, centralizing comprehensive guides and API references into a new, dedicated API reference section under `app/api-reference/adapters` and `pages/api-reference/adapters`. It moves detailed content on adapter configuration, creation, testing, routing, Partial Prerendering (PPR) implementation, and runtime integration from scattered locations into this structured area. The previous `adapterPath` documentation now serves as an entry point, linking to the new, expanded content, and all existing internal links referencing adapter-related information have been updated to reflect these new paths. This **documentation improvement** enhances the discoverability and clarity for developers building or integrating custom deployment solutions for Next.js applications.

This commit introduces a **CI/CD workflow optimization** by conditionally executing the `upload-adapter-test-results` job within the **end-to-end deployment and release workflow**. The configuration in `.github/workflows/test_e2e_deploy_release.yml` is updated to ensure that **adapter test results** are only uploaded when the workflow is triggered from the `canary` branch. This **maintenance** change applies to both `workflow_dispatch` and `release` events targeting `canary`, preventing unnecessary data uploads for non-canary builds and streamlining the CI process.

test: scope css data-url typing to fixture (#91877)

This commit introduces a **new capability** to automatically upload **adapter deploy test results** within the CI/CD pipeline. It modifies the **GitHub Actions workflows** (`.github/workflows/build_reusable.yml` and `.github/workflows/test_e2e_deploy_release.yml`) to include steps for collecting, zipping, and uploading these results as artifacts. A new Node.js script, `scripts/upload-adapter-test-results.mjs`, is added to handle the collection and archiving of JSON test files. This enhancement streamlines the comparison and analysis of adapter performance over time by making test outcomes readily available.

This commit **fixes** an issue where `compilerOptions.baseUrl` inherited via `extends` in `tsconfig.json` was not correctly handled, leading to TS6 deprecation warnings. It refactors the **TypeScript configuration parsing** within `packages/next/src/lib/typescript/getTypeScriptConfiguration.ts` to properly resolve the base URL and rewrite `paths` accordingly. This **compatibility update** ensures **correct import alias resolution** and prevents TS5101 errors during typechecking, maintaining robust project setup with newer TypeScript versions.

This commit performs a **dependency update** for the **Next.js integration**, specifically bumping the `@next-community/adapter-vercel` development dependency from `0.0.1-beta.14` to `0.0.1-beta.15` within the `packages/next` module. This **maintenance chore** ensures the project utilizes the latest version of the Next.js adapter, incorporating any recent bug fixes, performance improvements, or new features. The update helps maintain optimal compatibility and functionality with the Next.js ecosystem, and a corresponding **documentation** entry has been added to reflect this change.

This commit performs a **maintenance update** to the **Next.js TypeScript configuration defaults** to ensure compatibility with modern TypeScript versions, particularly TypeScript 6+. It addresses the deprecation of `moduleResolution: "node10"` by automatically configuring `moduleResolution: "bundler"` for modern module modes, while gracefully falling back to `"node"` for `commonjs`/`amd` configurations. This **prevents potential `TS5107` build failures** and adapts `getTypeScriptConfiguration.ts` to handle other deprecated `tsconfig` options like `target` and `baseUrl`. The changes ensure a smoother development experience for users leveraging newer TypeScript features within Next.js projects, with updated tests reflecting these new defaults.

This commit delivers a **bug fix** to the **`@nx/builders`** package, specifically enhancing the `node-module-esbuild-plugin`. It addresses an issue where the build system failed to correctly detect Node.js built-in module usage when `esbuild` and the package resolver interpreted a package's entry fields differently, leading to potential build errors. The fix involves introducing a new helper function, `getPackageNameFromSpecifier`, and improving the plugin's logic to record additional package edges for more robust built-in usage detection. This change prevents incorrect bundling and build failures for projects using packages with divergent entry point configurations, and is validated by new and stabilized **test cases** within the `builders` and `core` E2E suites.

This commit **refactors** the **Next.js server build process** by **removing an environment variable check** that previously governed the activation of the minimal server bundling feature. Specifically, it simplifies the `useBundledServer` condition in `packages/next/src/server-build.ts`, allowing the feature to activate automatically on compatible Next.js versions. This change **fixes an issue** related to merging `next-minimal-server.js.nft.json` into the server trace, ensuring more reliable and consistent server trace generation for bundled servers. The overall impact is a streamlined and more robust server build configuration for Next.js applications.

This commit **stabilizes deferred workflow discovery** within **Next.js applications**, particularly for **canary builds** and **e2e tests**, by addressing several underlying issues. It introduces robust `tsconfig` resolution for symlinked configurations, refines workflow alias handling, and implements retry logic and improved implicit step file resolution within the **Next.js builder's deferred discovery mechanism**. Additionally, it enhances the lookup of **builtin response steps** in the **core SDK** and adjusts workflow metadata handling to improve local development and testing reliability. This comprehensive **bug fix** and **stabilization** effort ensures consistent and reliable workflow execution across different Next.js build environments, including webpack and turbopack.

This commit **fixes a bug** in the **Next.js build process** where **dynamic metadata routes** were incorrectly omitted from **adapter `onBuildComplete` outputs**. Previously, the `handleBuildComplete` function too aggressively skipped routes like `robots.txt` and `sitemap.xml` if they were dynamically generated, preventing them from appearing in `outputs.appRoutes`. The fix ensures that only truly prerendered or static metadata files are excluded, allowing **adapters** to correctly identify and process all **dynamic metadata routes**. This is crucial for **deployment and build tools** that rely on accurate route information provided by the adapter's build complete hook.

This commit **fixes a bug** in **OpenTelemetry instrumentation** within Next.js, ensuring that **span names correctly include route information** even when `handler` exports are invoked directly, bypassing the `base-server`. Previously, these spans would only contain the HTTP method, leading to incomplete tracing data. The fix specifically targets the `pages-handler.ts` module to properly propagate route details. This enhancement improves **observability and traceability** for applications utilizing custom server setups or serverless functions that directly call Next.js handlers, with new E2E tests added to verify correct span naming and context propagation.

This commit **fixes** an issue in **Next.js's routing system** where **dynamic route parameters** containing encoded default placeholders were not correctly normalized. The `normalizeDynamicRouteParams` function in `packages/next/src/server/server-utils.ts` was updated to properly handle both singly and doubly encoded values, ensuring accurate route matching. This **bug fix** improves the robustness of App Router dynamic segments, especially when used with `vary-params` and revalidation. Extensive new **end-to-end tests** were added to validate this behavior and prevent regressions, specifically targeting dynamic segment params with time-based revalidation.

This commit introduces a **fix** to correctly handle **encoded dynamic placeholders** within **app routes**, such as `[project]`, by normalizing them before parsing route segments. A new utility function, `normalizeEncodedDynamicPlaceholder`, is integrated into the `parseAppRoute` logic in `packages/next/src/shared/lib/router/routes/app.ts` to ensure these segments are always interpreted correctly. This **enhances the robustness of app route parsing** and **fallback parameter resolution**, preventing issues where encoded placeholders might lead to incorrect routing. Additionally, **regression tests** have been added to cover encoded placeholder inputs for fallback parameters and to assert that vary-param segment prefetch responses do not contain encoded root parameter placeholders.

This commit introduces a **feature enhancement** to the **Edge Runtime build process**, providing a stable and canonical way to identify edge function entrypoints. It adds an `entrypoint` field to the `EdgeFunctionDefinition` within the **middleware manifest** for app, pages, and middleware edge functions, ensuring consistent population across webpack and Turbopack. This critical metadata is then exposed via `build-complete` as `edgeRuntime` fields in **adapter outputs**, including `modulePath`, `entryKey`, and `handlerExport`. This change allows **adapter consumers** to reliably load and invoke edge functions without depending on internal `next-server` sandbox handling or brittle bundler-specific file names, significantly improving **stability and compatibility** for Edge Function execution.

This commit **enhances the Next.js edge runtime** by wiring custom `cacheHandler` and `cacheHandlers` through all remaining edge entrypoints, including **edge app pages, edge app routes, edge pages SSR, middleware, and edge API routes**. This **feature enhancement** ensures that custom caching logic is consistently applied across all edge environments, addressing previous gaps where these handlers were not forwarded. The change involves modifications to **Turbopack/Rust entry generation**, webpack templates, and the `edge-route-module-wrapper.ts`, and is accompanied by a comprehensive **e2e regression test suite** (`test/e2e/cache-handlers-upstream-wiring`) to validate correct behavior for both pages and app router, edge and non-edge paths, and revalidation scenarios.

This commit introduces a **new capability** to the **`@next/routing`** package by enhancing the `resolveRoutes()` function to return more precise and complete route resolution data. It renames `matchedPathname` to **`resolvedPathname`**, adds **`resolvedQuery`** to include merged query parameters, and crucially, introduces **`invocationTarget`** to specify the concrete pathname and query that should be invoked after rewrites and dynamic matches. This **feature enhancement** provides adapters and consumers with the exact information needed for route invocation, eliminating the ambiguity of dynamic routes and the need for manual reconstruction of merged query parameters, thereby making the package **easier to consume**. The change also involves **refactoring** by removing the `query` alias for consistency and updating public types, documentation, and tests to reflect these new fields.

This commit introduces a **new capability** by exposing critical **router helpers** like `hostname`, `revalidate`, and `render404` through the `requestMeta` object, making them available for **Node.js adapters** when invoking the handler directly. It enhances the **server-side routing context** by updating route modules to merge these request-scoped `requestMeta` values with the existing router server context fallback. This provides **adapters** with a public API to pass previously internal router functionalities, improving flexibility for custom environments. The **`adapterPath` documentation** has been updated to reflect this new contract, alongside minor **refactoring** to standardize `revalidate` parameter names across the codebase.