Developer
Josh Story
story@hey.com
Performance
YoY:+569%Key patterns and highlights from this developer's activity.
Breakdown of growth, maintenance, and fixes effort over time.
Bugs introduced vs. fixed over time.
Reclassifies engineering effort based on bug attribution. Commits that introduced bugs are retrospectively counted as poor investments.
Investment Quality reclassifies engineering effort based on bug attribution data. Commits identified as buggy origins (those that introduced bugs later fixed by someone) have their grow and maintenance time moved into the Wasted Time category. Their waste (fix commits) remains counted as productive. All other commits retain their standard classification: grow is productive, maintenance is maintenance, and waste (fixes) is productive.
The standard model classifies commits as Growth, Maintenance, or Fixes. Investment Quality adds a quality lens: a commit that introduced a bug is retrospectively counted as a poor investment — the engineering time spent on it was wasted because it ultimately required additional fix work. Fix commits (Fixes in the standard model) are reframed as productive, because fixing bugs is valuable work.
Currently computed client-side from commit and bug attribution data. Ideal server-side endpoint:
POST /v1/organizations/{orgId}/investment-quality
Content-Type: application/json
Request:
{
"startTime": "2025-01-01T00:00:00Z",
"endTime": "2025-12-31T23:59:59Z",
"bucketSize": "BUCKET_SIZE_MONTH",
"groupBy": ["repository_id" | "deliverer_email"]
}
Response:
{
"productivePct": 74,
"maintenancePct": 18,
"wastedPct": 8,
"buckets": [
{
"bucketStart": "2025-01-01T00:00:00Z",
"productive": 4.2,
"maintenance": 1.8,
"wasted": 0.6
}
]
}Latest analyzed commits from this developer.
| Hash | Message | Date | Files | Effort |
|---|---|---|---|---|
| 468de5d | This commit **refactors** the **Next.js core** by removing the explicit `workStore` parameter from numerous functions responsible for creating `params`, `searchParams`, and `pathname` across the framework. Instead of being passed explicitly, `workStore` is now retrieved idiomatically from `workAsyncStorage.getStore()` internally within these functions, simplifying their signatures and **reducing boilerplate** for callers. This change impacts **client and server components**, **metadata resolution**, and various **server-side request processing** utilities, and includes a **new error code** for uninitialized `workStore` access. Ultimately, this is a step towards enabling **metadata components** to render directly without requiring factory closures. | Feb 20 | 12 | maint |
| ca0957d | This commit **fixes a critical bug** in the **Next.js server runtime** that caused stack overflows due to the `unhandled-rejection` module being bundled and loaded twice, leading to mutual recursion. To resolve this, the `unhandled-rejection` module is **externalized** by renaming it to `unhandled-rejection.external.tsx`, ensuring it is loaded only once and preventing the double-installation issue. Furthermore, **robustness improvements** include a global symbol guard to prevent re-installation and a reentrancy guard on the handler, safeguarding against synchronous re-emissions. This significantly enhances the stability of **server processes** by preventing crashes from unhandled promise rejections and introduces a new error code for detecting such issues. | Feb 20 | 5 | maint |
| 2bf2c9c | This commit introduces a significant **refactoring** to the **Next.js metadata and viewport tag rendering logic**, simplifying its internal architecture. It replaces a complex, layered component-based abstraction with a single, flat imperative function that constructs the tags array using explicit JSX, if-checks, and for-loops. This change primarily impacts `packages/next/src/lib/metadata/metadata.tsx`, specifically functions like `renderMetadata` and `renderViewport`, making all meta/link tags explicitly visible at their call site. The rewrite also enumerates Open Graph and AppLinks properties explicitly, rather than iterating generically, and optimizes key assignment by eliminating the `cloneElement` pass, leading to a more transparent and potentially more performant rendering process for **HTML metadata**. | Feb 20 | 7 | maint |
| 38cd020 | This commit **fixes** an issue in **React's server-side rendering (SSR) with Suspense** where boundaries were unnecessarily outlined due to "suspensey" CSS during the initial shell flush, leading to higher-level fallbacks being displayed prematurely. It introduces a `flushingInShell` flag, passed to the `hasSuspenseyContent` function in the **Fizz server renderer** and **DOM host configuration**, to prevent outlining for stylesheet-only suspensey content when flushing the shell. This change improves the **user experience** by ensuring more granular fallbacks are shown, as stylesheets emitted in the `<head>` already block paint. While suspensey images still trigger outlining for ViewTransition animations, the behavior for streamed completions, where suspensey CSS still causes outlining, remains unaffected. | Feb 19 | 6 | waste |
| ea3cad2 | This commit **refines the validation of synchronous I/O (sync IO)** within the **Next.js App Router's runtime prefetching** mechanism. Previously, sync IO after runtime data access would error across the entire route if any segment was configured for runtime prefetching, making adoption difficult. This **enhancement** now restricts sync IO errors only to segments that are *actually* runtime prefetched and their descendants, significantly **simplifying the integration of runtime prefetching** for specific parts of an application. It introduces new **`EarlyStatic` and `EarlyRuntime` rendering stages** to enable this granular validation and updates various request utilities like `cookies`, `headers`, and `params` to respect these new stages and prefetchability. This **refactoring** of the rendering pipeline makes runtime prefetching more practical by reducing the burden of fixing sync IO across the entire segment stack. | Feb 18 | 24 | maint |
| 78f13e0 | This commit implements a **fix** to enhance the robustness of the **Staged Rendering Controller** in **Next.js server-side rendering**. It ensures that upon receiving an `AbortSignal`, all outstanding **stage promises**, encompassing both runtime and dynamic types, are **unconditionally rejected**. Specifically, the changes in `packages/next/src/server/app-render/staged-rendering.ts` remove conditional checks to guarantee these promises do not remain in a perpetually pending state. This improvement prevents potential resource leaks or stalled rendering processes, leading to more reliable and efficient handling of aborted rendering operations. | Feb 18 | 1 | waste |
| 715103a | This commit **refactors** the **Next.js server-side rendering (SSR) and prerendering pipeline** by **unifying sequential task execution** under a single `runInSequentialTasks` utility. The `runInSequentialTasks` utility in `app-render-render-utils.ts` is enhanced to correctly handle thenable results and suppress unhandled rejections, while removing the redundant `scheduleInSequentialTasks`. This **refactoring** standardizes how sequential tasks are managed across various rendering functions, including `stagedRenderToReadableStreamWithoutCachesInDev` and `prerenderToStream`, improving code consistency and maintainability within the `app-render` module. | Feb 18 | 4 | maint |
| 6df47fc | This commit performs a significant **refactoring** of the **task pipelining mechanism** within **Next.js's server-side rendering (SSR) and app-render processes**. The utility `pipelineInSequentialTasks` is renamed and restructured to `runInSequentialTasks`, allowing for an arbitrary number of sequential tasks and ensuring all tasks, including the final user-provided one, receive "Fast Immediate" treatment for **improved performance**. This change also introduces a **new error (1054)** to explicitly prevent `runInSequentialTasks` from being invoked in the **edge runtime**, clarifying its intended execution environment. Key functions like `renderWithRestartOnCacheMissInDev` and `collectStagedSegmentData` are updated to utilize this enhanced pipelining utility. | Feb 17 | 4 | maint |
| e5e0d35 | This commit **refactors** the **runtime prerendering mechanism** in Next.js to leverage the `StagedRenderingController` for managing rendering stages. It integrates the `StagedRenderingController` into the **`app-render`** and **`dynamic-rendering`** modules, replacing direct promise-based stage management with a more robust system for build and runtime prerendering. This **internal architectural improvement** prepares the rendering pipeline for more advanced sync I/O error handling and complex stage transitions. Furthermore, the private cache store is updated to remove the redundant `runtimeStagePromise`, ensuring nested caches correctly await the outer store's runtime stage. | Feb 17 | 6 | maint |
| d45f83f | This commit **refactors** the mechanism for signaling **render abandonment** within the Next.js **server-side rendering** pipeline. It introduces an explicit `AbortController` and its `signal` to manage render interruptions, replacing the previous implicit `mayAbandon` flag and direct abandonment calls. This change primarily affects the `StagedRenderingController` in `staged-rendering.ts` and its usage in `app-render.tsx`, improving the clarity and robustness of the abandonment interface. The update prepares the `StagedRenderingController` for broader use cases, including future **production prerendering** and runtime prefetches. | Feb 13 | 2 | maint |
| e6d27d4 | This commit performs a **refactoring** to enhance **code clarity** within the **Next.js server-side Node.js environment extensions**. It renames a utility file, previously ambiguously named `utils`, to `io-utils` to more accurately reflect its synchronous I/O related contents. Consequently, several modules within the `node-environment-extensions` directory, including `date`, `node-crypto`, `random`, and `web-crypto`, have their import paths updated from `./utils` to `./io-utils`. This internal change improves discoverability for developers working on the **Next.js core** without altering any runtime behavior or introducing functional changes to the framework. | Feb 13 | 5 | maint |
| db71391 | This commit **enhances the React Fiber runtime** by ensuring that the thenable returned by a **lazy initializer** (e.g., `React.lazy`) is **unconditionally instrumented** in all environments, rather than only in development builds with specific debug flags. This change is critical for enabling the `SuspendOnImmediate` optimization, which allows the runtime to **resume rendering immediately** if a lazy component resolves before the stack unwinds. By making this optimization pathway available universally, it facilitates robust testing and production use of features like `useId` that rely on quick resolution, and simplifies development by allowing standard Promises to be used with `React.lazy` without custom instrumentation workarounds. | Jan 16 | 2 | waste |
| f0fbb0d | This commit **fixes a bug** in the **React Fiber reconciler** where the `Forked` flag was incorrectly stripped from Fibers during work replay after suspension. By including the `Forked` flag in the `StaticMask` within `ReactFiberFlags.js`, the system now correctly preserves this flag's state, which is crucial for maintaining proper tree context. This ensures **consistent and correct `useId` tracking** in server-rendered applications, especially when components suspend and resume. A new test case in `ReactDOMFizzServer-test.js` validates `useId` behavior with suspended and lazy-loaded siblings, confirming the fix's effectiveness. | Jan 16 | 2 | waste |
| c186624 | This commit **fixes a critical hydration bug** within the **React Fiber reconciler** that could lead to **hydration errors** when a `HostComponent` suspends and then immediately resolves during the hydration process. Previously, this scenario could cause the hydration cursor to become offset due to incomplete unwinding of work. The **bug fix** introduces a new function, `popHydrationStateOnInterruptedWork`, to correctly restore the hydration cursor's position when replaying interrupted work, which is integrated into the `replayBeginWork` process. This ensures **robust and accurate server-side rendering (SSR) hydration**, preventing mismatches and improving the stability of applications using suspending components. New test cases were added to validate the correct behavior across various component types, including `HostSingleton`, `Suspense`, and `Activity` components. | Jan 13 | 3 | waste |
| 69d9d29 | This commit implements a **critical security fix** by **disallowing `javascript:` URLs** across various Next.js routing mechanisms and redirects. It prevents their use in the `Link` component's `href` and `as` props, `router.push`, `router.replace`, and `router.prefetch` methods for both App and Pages Routers, and within server action redirects. This **bug fix** enhances application security by preventing potential XSS vulnerabilities, treating `javascript:` URLs as non-routable and introducing a new utility function `isJavaScriptURLString` and error code for detection. The change ensures that Next.js APIs align with React's existing prohibition, improving the overall robustness of URL handling and protecting users from malicious scripts. | Jan 7 | 24 | waste |
| c0c75e4 | This commit introduces a significant **refactoring** to how **React instances** are managed and accessed within the Next.js server runtime, particularly for **error reporting** and **owner stack capturing**. It replaces the complex `AsyncLocalStorage`-based proxying of `captureOwnerStack()` through the `workUnitStore` with a simpler mechanism that directly registers and retrieves client and server React instances via new global utility functions like `registerServerReact` and `getClientReact`. This **architectural improvement** simplifies the plumbing for external code, such as patched I/O methods in `node-environment-extensions`, to correctly attribute errors to the appropriate React component owner in both **SSR** and **RSC** contexts. The change enhances the maintainability and robustness of error reporting by providing a more direct and less error-prone way to access React's internal state. | Oct 29 | 9 | maint |
| 1b45163 | This commit **adjusts the Next.js bundling process** by **excluding the `next-js` condition** for **middleware, proxy, and instrumentation** entrypoints. This **bug fix** addresses an inconsistency where these environments, lacking full Next.js API support, were incorrectly bundled with the condition, causing potential runtime issues for third-party libraries. By modifying `next-core`'s edge and server context resolution, the change ensures that external packages can reliably target Next.js with consistent API expectations across all environments. This significantly improves **developer experience** and **ecosystem compatibility**, validated by comprehensive new end-to-end tests. | Oct 27 | 87 | maint |
| 3dafab9 | This commit **corrects an incorrect invariant** within the **Cache Components**' `cacheLife` configuration, which previously mandated that the `stale` duration must exceed the `expire` duration. Recognizing that `stale` and `expire` describe distinct cache entry lifetimes (client read vs. cache creation, respectively), this change **removes the erroneous requirement**. This **bug fix** enhances the **flexibility and correctness of cache behavior**, allowing for more logical and independent configuration of cache entry expiration and staleness. The change **improves cache configuration options** and prevents misinterpretations of cache entry lifetimes. | Oct 21 | 2 | – |
| e2d6ff9 | This commit **updates the React channel usage** for **Cache Components** when **partial prerendering (PPR)** is enabled, shifting from experimental to the more stable **canary channel**. It modifies the `next-core` crate's import map generation (`get_next_client_import_map`, `apply_vendored_react_aliases_server`) to prioritize canary React. Additionally, the `needsExperimentalReact` function in `packages/next/src/lib/needs-experimental-react.ts` is refined to only require experimental React if the `taint` feature is active, removing PPR as a condition. This **feature enhancement** leverages React's stabilization of PPR, providing a more stable default experience for users while retaining flexibility for bleeding-edge experimental features. | Oct 18 | 2 | grow |
| 49fcbd9 | This commit introduces a **developer experience improvement** to the **Next.js server-side rendering pipeline** by **skipping cache warming** when caches are explicitly disabled in development mode. Previously, disabling caches would force every request to block while refilling empty caches, leading to slow renders. Now, the system detects this scenario via `isBypassingCachesInDev` in `app-render.tsx` and proceeds without warming, ensuring faster streaming. This **new capability** includes a console warning (`WarnForBypassCachesInDev`) about inaccurate React DevTools metadata and is covered by **new documentation** and **end-to-end tests**. | Oct 18 | 8 | maint |
This commit **refactors** the **Next.js core** by removing the explicit `workStore` parameter from numerous functions responsible for creating `params`, `searchParams`, and `pathname` across the framework. Instead of being passed explicitly, `workStore` is now retrieved idiomatically from `workAsyncStorage.getStore()` internally within these functions, simplifying their signatures and **reducing boilerplate** for callers. This change impacts **client and server components**, **metadata resolution**, and various **server-side request processing** utilities, and includes a **new error code** for uninitialized `workStore` access. Ultimately, this is a step towards enabling **metadata components** to render directly without requiring factory closures.
This commit **fixes a critical bug** in the **Next.js server runtime** that caused stack overflows due to the `unhandled-rejection` module being bundled and loaded twice, leading to mutual recursion. To resolve this, the `unhandled-rejection` module is **externalized** by renaming it to `unhandled-rejection.external.tsx`, ensuring it is loaded only once and preventing the double-installation issue. Furthermore, **robustness improvements** include a global symbol guard to prevent re-installation and a reentrancy guard on the handler, safeguarding against synchronous re-emissions. This significantly enhances the stability of **server processes** by preventing crashes from unhandled promise rejections and introduces a new error code for detecting such issues.
This commit introduces a significant **refactoring** to the **Next.js metadata and viewport tag rendering logic**, simplifying its internal architecture. It replaces a complex, layered component-based abstraction with a single, flat imperative function that constructs the tags array using explicit JSX, if-checks, and for-loops. This change primarily impacts `packages/next/src/lib/metadata/metadata.tsx`, specifically functions like `renderMetadata` and `renderViewport`, making all meta/link tags explicitly visible at their call site. The rewrite also enumerates Open Graph and AppLinks properties explicitly, rather than iterating generically, and optimizes key assignment by eliminating the `cloneElement` pass, leading to a more transparent and potentially more performant rendering process for **HTML metadata**.
This commit **fixes** an issue in **React's server-side rendering (SSR) with Suspense** where boundaries were unnecessarily outlined due to "suspensey" CSS during the initial shell flush, leading to higher-level fallbacks being displayed prematurely. It introduces a `flushingInShell` flag, passed to the `hasSuspenseyContent` function in the **Fizz server renderer** and **DOM host configuration**, to prevent outlining for stylesheet-only suspensey content when flushing the shell. This change improves the **user experience** by ensuring more granular fallbacks are shown, as stylesheets emitted in the `<head>` already block paint. While suspensey images still trigger outlining for ViewTransition animations, the behavior for streamed completions, where suspensey CSS still causes outlining, remains unaffected.
This commit **refines the validation of synchronous I/O (sync IO)** within the **Next.js App Router's runtime prefetching** mechanism. Previously, sync IO after runtime data access would error across the entire route if any segment was configured for runtime prefetching, making adoption difficult. This **enhancement** now restricts sync IO errors only to segments that are *actually* runtime prefetched and their descendants, significantly **simplifying the integration of runtime prefetching** for specific parts of an application. It introduces new **`EarlyStatic` and `EarlyRuntime` rendering stages** to enable this granular validation and updates various request utilities like `cookies`, `headers`, and `params` to respect these new stages and prefetchability. This **refactoring** of the rendering pipeline makes runtime prefetching more practical by reducing the burden of fixing sync IO across the entire segment stack.
This commit implements a **fix** to enhance the robustness of the **Staged Rendering Controller** in **Next.js server-side rendering**. It ensures that upon receiving an `AbortSignal`, all outstanding **stage promises**, encompassing both runtime and dynamic types, are **unconditionally rejected**. Specifically, the changes in `packages/next/src/server/app-render/staged-rendering.ts` remove conditional checks to guarantee these promises do not remain in a perpetually pending state. This improvement prevents potential resource leaks or stalled rendering processes, leading to more reliable and efficient handling of aborted rendering operations.
This commit **refactors** the **Next.js server-side rendering (SSR) and prerendering pipeline** by **unifying sequential task execution** under a single `runInSequentialTasks` utility. The `runInSequentialTasks` utility in `app-render-render-utils.ts` is enhanced to correctly handle thenable results and suppress unhandled rejections, while removing the redundant `scheduleInSequentialTasks`. This **refactoring** standardizes how sequential tasks are managed across various rendering functions, including `stagedRenderToReadableStreamWithoutCachesInDev` and `prerenderToStream`, improving code consistency and maintainability within the `app-render` module.
This commit performs a significant **refactoring** of the **task pipelining mechanism** within **Next.js's server-side rendering (SSR) and app-render processes**. The utility `pipelineInSequentialTasks` is renamed and restructured to `runInSequentialTasks`, allowing for an arbitrary number of sequential tasks and ensuring all tasks, including the final user-provided one, receive "Fast Immediate" treatment for **improved performance**. This change also introduces a **new error (1054)** to explicitly prevent `runInSequentialTasks` from being invoked in the **edge runtime**, clarifying its intended execution environment. Key functions like `renderWithRestartOnCacheMissInDev` and `collectStagedSegmentData` are updated to utilize this enhanced pipelining utility.
This commit **refactors** the **runtime prerendering mechanism** in Next.js to leverage the `StagedRenderingController` for managing rendering stages. It integrates the `StagedRenderingController` into the **`app-render`** and **`dynamic-rendering`** modules, replacing direct promise-based stage management with a more robust system for build and runtime prerendering. This **internal architectural improvement** prepares the rendering pipeline for more advanced sync I/O error handling and complex stage transitions. Furthermore, the private cache store is updated to remove the redundant `runtimeStagePromise`, ensuring nested caches correctly await the outer store's runtime stage.
This commit **refactors** the mechanism for signaling **render abandonment** within the Next.js **server-side rendering** pipeline. It introduces an explicit `AbortController` and its `signal` to manage render interruptions, replacing the previous implicit `mayAbandon` flag and direct abandonment calls. This change primarily affects the `StagedRenderingController` in `staged-rendering.ts` and its usage in `app-render.tsx`, improving the clarity and robustness of the abandonment interface. The update prepares the `StagedRenderingController` for broader use cases, including future **production prerendering** and runtime prefetches.
This commit performs a **refactoring** to enhance **code clarity** within the **Next.js server-side Node.js environment extensions**. It renames a utility file, previously ambiguously named `utils`, to `io-utils` to more accurately reflect its synchronous I/O related contents. Consequently, several modules within the `node-environment-extensions` directory, including `date`, `node-crypto`, `random`, and `web-crypto`, have their import paths updated from `./utils` to `./io-utils`. This internal change improves discoverability for developers working on the **Next.js core** without altering any runtime behavior or introducing functional changes to the framework.
This commit **enhances the React Fiber runtime** by ensuring that the thenable returned by a **lazy initializer** (e.g., `React.lazy`) is **unconditionally instrumented** in all environments, rather than only in development builds with specific debug flags. This change is critical for enabling the `SuspendOnImmediate` optimization, which allows the runtime to **resume rendering immediately** if a lazy component resolves before the stack unwinds. By making this optimization pathway available universally, it facilitates robust testing and production use of features like `useId` that rely on quick resolution, and simplifies development by allowing standard Promises to be used with `React.lazy` without custom instrumentation workarounds.
This commit **fixes a bug** in the **React Fiber reconciler** where the `Forked` flag was incorrectly stripped from Fibers during work replay after suspension. By including the `Forked` flag in the `StaticMask` within `ReactFiberFlags.js`, the system now correctly preserves this flag's state, which is crucial for maintaining proper tree context. This ensures **consistent and correct `useId` tracking** in server-rendered applications, especially when components suspend and resume. A new test case in `ReactDOMFizzServer-test.js` validates `useId` behavior with suspended and lazy-loaded siblings, confirming the fix's effectiveness.
This commit **fixes a critical hydration bug** within the **React Fiber reconciler** that could lead to **hydration errors** when a `HostComponent` suspends and then immediately resolves during the hydration process. Previously, this scenario could cause the hydration cursor to become offset due to incomplete unwinding of work. The **bug fix** introduces a new function, `popHydrationStateOnInterruptedWork`, to correctly restore the hydration cursor's position when replaying interrupted work, which is integrated into the `replayBeginWork` process. This ensures **robust and accurate server-side rendering (SSR) hydration**, preventing mismatches and improving the stability of applications using suspending components. New test cases were added to validate the correct behavior across various component types, including `HostSingleton`, `Suspense`, and `Activity` components.
This commit implements a **critical security fix** by **disallowing `javascript:` URLs** across various Next.js routing mechanisms and redirects. It prevents their use in the `Link` component's `href` and `as` props, `router.push`, `router.replace`, and `router.prefetch` methods for both App and Pages Routers, and within server action redirects. This **bug fix** enhances application security by preventing potential XSS vulnerabilities, treating `javascript:` URLs as non-routable and introducing a new utility function `isJavaScriptURLString` and error code for detection. The change ensures that Next.js APIs align with React's existing prohibition, improving the overall robustness of URL handling and protecting users from malicious scripts.
This commit introduces a significant **refactoring** to how **React instances** are managed and accessed within the Next.js server runtime, particularly for **error reporting** and **owner stack capturing**. It replaces the complex `AsyncLocalStorage`-based proxying of `captureOwnerStack()` through the `workUnitStore` with a simpler mechanism that directly registers and retrieves client and server React instances via new global utility functions like `registerServerReact` and `getClientReact`. This **architectural improvement** simplifies the plumbing for external code, such as patched I/O methods in `node-environment-extensions`, to correctly attribute errors to the appropriate React component owner in both **SSR** and **RSC** contexts. The change enhances the maintainability and robustness of error reporting by providing a more direct and less error-prone way to access React's internal state.
This commit **adjusts the Next.js bundling process** by **excluding the `next-js` condition** for **middleware, proxy, and instrumentation** entrypoints. This **bug fix** addresses an inconsistency where these environments, lacking full Next.js API support, were incorrectly bundled with the condition, causing potential runtime issues for third-party libraries. By modifying `next-core`'s edge and server context resolution, the change ensures that external packages can reliably target Next.js with consistent API expectations across all environments. This significantly improves **developer experience** and **ecosystem compatibility**, validated by comprehensive new end-to-end tests.
This commit **corrects an incorrect invariant** within the **Cache Components**' `cacheLife` configuration, which previously mandated that the `stale` duration must exceed the `expire` duration. Recognizing that `stale` and `expire` describe distinct cache entry lifetimes (client read vs. cache creation, respectively), this change **removes the erroneous requirement**. This **bug fix** enhances the **flexibility and correctness of cache behavior**, allowing for more logical and independent configuration of cache entry expiration and staleness. The change **improves cache configuration options** and prevents misinterpretations of cache entry lifetimes.
This commit **updates the React channel usage** for **Cache Components** when **partial prerendering (PPR)** is enabled, shifting from experimental to the more stable **canary channel**. It modifies the `next-core` crate's import map generation (`get_next_client_import_map`, `apply_vendored_react_aliases_server`) to prioritize canary React. Additionally, the `needsExperimentalReact` function in `packages/next/src/lib/needs-experimental-react.ts` is refined to only require experimental React if the `taint` feature is active, removing PPR as a condition. This **feature enhancement** leverages React's stabilization of PPR, providing a more stable default experience for users while retaining flexibility for bleeding-edge experimental features.
This commit introduces a **developer experience improvement** to the **Next.js server-side rendering pipeline** by **skipping cache warming** when caches are explicitly disabled in development mode. Previously, disabling caches would force every request to block while refilling empty caches, leading to slow renders. Now, the system detects this scenario via `isBypassingCachesInDev` in `app-render.tsx` and proceeds without warming, ensuring faster streaming. This **new capability** includes a console warning (`WarnForBypassCachesInDev`) about inaccurate React DevTools metadata and is covered by **new documentation** and **end-to-end tests**.
Commit activity distribution by hour and day of week. Shows when this developer is most active.
Developers who frequently work on the same files and symbols. Higher score means stronger code collaboration.