Epic: Hacker News RSC Demo for React on Rails Pro

[justin808]

Hacker News RSC Demo

Build a React on Rails Pro (RSC) version of the Vercel Hacker News app.

Reference Implementation

• Source: https://github.com/vercel/next-react-server-components
• Live Demo: https://next-rsc-hn.vercel.app

Progress Tracking

Phase 1: Foundation

• 1.1: Initialize Rails 8 Application with React on Rails Pro #71 - 1.1: Initialize Rails 8 Application with React on Rails Pro
• 1.2: Configure CSS Modules #72 - 1.2: Configure CSS Modules
• 1.3: Set Up TypeScript Configuration #73 - 1.3: Set Up TypeScript Configuration

Phase 2: Data Layer

• 2.1: Create Hacker News API Client #74 - 2.1: Create Hacker News API Client
• 2.2: Create Story Presenter #75 - 2.2: Create Story Presenter
• 2.3: Create Comment Presenter #76 - 2.3: Create Comment Presenter
• 2.4: Create User Presenter #77 - 2.4: Create User Presenter

Phase 3: Rails Controllers & Routes

• 3.1: Create Stories Controller with RSC Rendering #78 - 3.1: Create Stories Controller with RSC Rendering
• 3.2: Create Items Controller (Story Detail) #79 - 3.2: Create Items Controller (Story Detail)
• 3.3: Create Users Controller #80 - 3.3: Create Users Controller
• 3.4: Configure Routes #81 - 3.4: Configure Routes

Phase 4: React Server Components

• 4.1: Create Root Layout Component #82 - 4.1: Create Root Layout Component
• 4.2: Create Header Component #83 - 4.2: Create Header Component
• 4.3: Create Footer Component #84 - 4.3: Create Footer Component
• 4.4: Create Story List Component #85 - 4.4: Create Story List Component
• 4.5: Create Individual Story Component #86 - 4.5: Create Individual Story Component
• 4.6: Create Pagination Component #87 - 4.6: Create Pagination Component
• 4.7: Create Item Detail Page Component #88 - 4.7: Create Item Detail Page Component
• 4.8: Create Comment Component (Recursive) #89 - 4.8: Create Comment Component (Recursive)
• 4.9: Create Comment Toggle Client Component #90 - 4.9: Create Comment Toggle Client Component
• 4.10: Create User Profile Page Component #91 - 4.10: Create User Profile Page Component
• 4.11: Create Loading Skeletons #92 - 4.11: Create Loading Skeletons
• 4.12: Create Error Boundary Component #93 - 4.12: Create Error Boundary Component

Phase 5: Utilities

• 5.1: Create Time Ago Utility #94 - 5.1: Create Time Ago Utility
• 5.2: Create URL Domain Extractor #95 - 5.2: Create URL Domain Extractor

Phase 6: Streaming & Performance

• 6.1: Implement Streaming for Story List #96 - 6.1: Implement Streaming for Story List
• 6.2: Implement Streaming for Comments #97 - 6.2: Implement Streaming for Comments
• 6.3: Add HTTP Caching Headers #98 - 6.3: Add HTTP Caching Headers

Phase 7: Polish & Production Ready

• 7.1: Add Meta Tags and SEO #99 - 7.1: Add Meta Tags and SEO
• 7.2: Add Responsive Design #100 - 7.2: Add Responsive Design
• 7.3: Write Integration Tests #101 - 7.3: Write Integration Tests
• 7.4: Add Production Configuration #102 - 7.4: Add Production Configuration
• 7.5: Create README Documentation #103 - 7.5: Create README Documentation

Dependency Graph

Phase 1 (Foundation)
├── #71 Rails + RoR Pro Setup ──┬──> #72 CSS Setup
│                               └──> #73 TypeScript Setup
│
├─────────────────────────────────────┐
│                                     │
v                                     v
Phase 2 (Data Layer)            Phase 3 (Controllers)
├── #74 HN API Client           ├── #78 Stories Controller
│         │                     │         │
│         v                     │         v
│    #75-#77 Presenters         │    #79-#81 Other Controllers
│                               │
└───────────────────────────────┘
            │
            v
Phase 4 (RSC Components)
├── #82 Layout ──> #83 Header, #84 Footer
├── #85 Stories ──> #86 Story, #87 Pagination
├── #88 ItemPage ──> #89 Comment ──> #90 CommentToggle
├── #91 UserPage, #92 Skeletons, #93 ErrorBoundary

Phase 5 (Utilities) - Parallel with Phase 4
├── #94 timeAgo
└── #95 urlUtils

Phase 6 (Streaming) - After Phase 4
├── #96 Story Streaming
├── #97 Comment Streaming
└── #98 Caching

Phase 7 (Polish) - Final phase
├── #99 SEO
├── #100 Responsive
├── #101 Tests
├── #102 Production Config
└── #103 Documentation

Parallelization Opportunities

Can run in parallel:

• 1.2: Configure CSS Modules #72 and 1.3: Set Up TypeScript Configuration #73 (after 1.1: Initialize Rails 8 Application with React on Rails Pro #71)
• Phase 2 (2.1: Create Hacker News API Client #74-2.4: Create User Presenter #77) and Phase 3 (3.1: Create Stories Controller with RSC Rendering #78-3.4: Configure Routes #81) after 1.1: Initialize Rails 8 Application with React on Rails Pro #71
• 4.2: Create Header Component #83, 4.3: Create Footer Component #84, 4.11: Create Loading Skeletons #92, 4.12: Create Error Boundary Component #93 (after 4.1: Create Root Layout Component #82)
• Phase 5 utilities (after 1.3: Set Up TypeScript Configuration #73)

Must be sequential:

• 1.1: Initialize Rails 8 Application with React on Rails Pro #71 → everything else
• 4.4: Create Story List Component #85 → 4.5: Create Individual Story Component #86, 4.6: Create Pagination Component #87
• 4.7: Create Item Detail Page Component #88 → 4.8: Create Comment Component (Recursive) #89 → 4.9: Create Comment Toggle Client Component #90

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and agent prompts for this issue.

• Create Plan

Examples

• Example 1
• Example 2

🔗 Similar & Duplicate Issues

Related Issues

• shakacode/react_on_rails-demos#71
• shakacode/react_on_rails#1672
• shakacode/react_on_rails#1782
• shakacode/react_on_rails-demos#78
• shakacode/react_on_rails-demos#72
• shakacode/react_on_rails#1949

🔗 Related PRs

shakacode/react_on_rails#1680 - Separate streamServerRenderedReactComponent from ReactOnRails [merged] | CHANGELOG.md:
"""

AI-generated summary of changes

The changes in the CHANGELOG.md file include the addition of a new version entry for 14.1.1, dated 2025-01-15. This entry introduces a fix that separates the streamServerRenderedReactComponent from the ReactOnRails object. This modification aims to prevent users from encountering errors during webpack compilation related to the absence of the stream-browserify package. The change is documented with a reference to the associated pull request (PR 1680) and the contributor's GitHub profile.

Alterations to the declarations of exported or public entities

• No alterations to the declarations of exported or public entities were made in this diff.
  """

---

node_package/src/ReactOnRails.ts:
"""

AI-generated summary of changes

The diff shows modifications to the ReactOnRails.ts file, specifically in the import statements and the implementation of the ReactOnRails object. The import of the Readable type from the stream module has been removed. The streamServerRenderedReactComponent function has been deleted from the exports of the ReactOnRails object, which previously allowed for server rendering of React components and returned a Readable stream. Instead, a new implementation of streamServerRenderedReactComponent has been added that throws an error indicating that streaming is only supported in Node.js environments. The serverRenderReactComponent function remains unchanged and continues to support server rendering without streaming. Overall, the changes indicate a shift away from streaming capabilities in the server rendering process while maintaining the existing functionality of the ReactOnRails object.

Alterations to the declarations of exported or public entities

• Method removed: streamServerRenderedReactComponent(options: RenderParams): Readable in ReactOnRails object in node_package/src/ReactOnRails.ts
• Method signature updated: streamServerRenderedReactComponent() in ReactOnRails object in node_package/src/ReactOnRails.ts → streamServerRenderedReactComponent(): void in ReactOnRails object in node_package/src/ReactOnRails.ts
  """

---

node_package/src/serverRenderReactComponent.ts:
"""

AI-generated summary of changes

The diff shows significant modifications to the serverRenderReactComponent.ts file, primarily involving the removal of several types and functions related to stream rendering, as well as the restructuring of imports. The PipeableStream and PassThrough imports from the stream module have been removed, indicating a shift away from stream-based rendering. The types StreamRenderState and associated logic for handling streaming results have been deleted, which simplifies the rendering process by focusing on direct rendering without streaming.

Additionally, the createResultObject function has been removed, along with its associated logic for handling stream results. The error handling and validation functions have been retained but are now imported from a new module, serverRenderUtils, which suggests a reorganization of utility functions for better modularity. The serverRenderReactComponent function has been preserved, but the logic for handling streams has been eliminated, indicating a potential simplification of the rendering process.

Overall, the changes reflect a move towards a more straightforward rendering approach, removing complexities associated with streaming and focusing on direct rendering of React components.

Alterations to the declarations of exported or public entities

• Method signature removed: const streamRenderReactComponent = (reactRenderingResult: ReactElement, options: RenderParams) in node_package/src/serverRenderReactComponent.ts
• Method signature removed: export const streamServerRenderedReactComponent = (options: RenderParams): Readable in node_package/src/serverRenderReactComponent.ts
  """

---

node_package/src/serverRenderUtils.ts:
"""

AI-generated summary of changes

The diff introduces several new functions and type imports in the node_package/src/serverRenderUtils.ts file. The createResultObject function constructs and returns a RenderResult object, encapsulating properties such as html, consoleReplayScript, and error handling details from the provided renderState. It checks for the presence of errors and includes a structured error message and stack if applicable. Additionally, it conditionally includes the isShellReady property based on its existence in the renderState.

The convertToError function is designed to standardize error handling by converting any input into an Error object, ensuring that if the input is already an Error, it is returned as is; otherwise, a new Error is created from the string representation of the input.

Lastly, the validateComponent function checks if a given RegisteredComponent is a renderer. If it is, the function throws an error with a specific message, indicating that a renderer was detected during server rendering, along with a link for further reference.

Overall, these additions enhance error handling and validation capabilities within the server rendering utilities.

Alterations to the declarations of exported or public entities

• Method added: createResultObject(html: string | null, consoleReplayScript: string, renderState: RenderState | StreamRenderState): RenderResult in node_package/src/serverRenderUtils.ts
• Method added: convertToError(e: unknown): Error in node_package/src/serverRenderUtils.ts
• Method added: validateComponent(componentObj: RegisteredComponent, componentName: string) in node_package/src/serverRenderUtils.ts
  """

---

node_package/src/streamServerRenderedReactComponent.ts:
"""

AI-generated summary of changes

The provided code introduces a new module for server-side rendering of React components using streams. It imports necessary libraries and types, including ReactDOMServer for rendering, stream utilities for handling data flow, and various utility functions for error handling and component validation.

The core functionality is encapsulated in the streamServerRenderedReactComponent function, which takes rendering options and attempts to retrieve a component from a registry. It validates the component and prepares it for rendering. If the rendering result is a server render hash or a promise, an error is thrown.

The rendering process is managed by the streamRenderReactComponent function, which utilizes ReactDOMServer.renderToPipeableStream to create a stream of the rendered component. This function handles various events such as onShellError, onShellReady, and onError, allowing for error management and transformation of the rendering output into a structured format.

The transformRenderStreamChunksToResultObject function processes the chunks of the rendering stream, converting them into a JSON format that includes console replay scripts and error handling. It creates a readable stream that can emit errors and manage the lifecycle of the rendering process.

Overall, the changes provide a robust mechanism for rendering React components on the server, with comprehensive error handling and streaming capabilities.

Alterations to the declarations of exported or public entities

• Method added: streamServerRenderedReactComponent(options: RenderParams): Readable in node_package/src/streamServerRenderedReactComponent.ts
  """

---

node_package/src/types/index.ts:
"""

AI-generated summary of changes

The diff introduces three new type definitions: RenderState, StreamRenderState, and RenderOptions in the node_package/src/types/index.ts file. The RenderState type defines the structure for the result of a render operation, which can be null, a string, or a Promise<string>, along with a boolean indicating if errors occurred and an optional RenderingError. The StreamRenderState type extends RenderState by omitting the result property and redefining it to be either null or a Readable stream, while also including an isShellReady boolean property. The RenderOptions type specifies options for rendering, including the component name, an optional DOM node ID, a trace flag, and a boolean indicating if rendering returns promises.

Additionally, the streamServerRenderedReactComponent method remains in the ReactOnRails interface, but the introduction of these new types suggests a more structured approach to handling rendering states and options. The overall structure of the ReactOnRails interface is maintained, but the new types enhance the clarity and granularity of the rendering logic.

Alterations to the declarations of exported or public entities

• New type added: RenderState in node_package/src/types/index.ts
• New type added: StreamRenderState in node_package/src/types/index.ts
• New type added: RenderOptions in node_package/src/types/index.ts
  """

---

node_package/tests/streamServerRenderedReactComponent.test.jsx:
"""

AI-generated summary of changes

The diff shows a modification in the import statement for the streamServerRenderedReactComponent function. The previous import statement used a named import syntax, while the updated version uses a default import syntax. This change does not affect the functionality of the code but alters how the streamServerRenderedReactComponent is imported from the module located at ../src/streamServerRenderedReactComponent.

No other functional changes, logic alterations, or error handling modifications are present in the provided code snippet. The structure and behavior of the tests remain unchanged, maintaining the same assertions and test cases.

Alterations to the declarations of exported or public entities

• Method signature updated: import { streamServerRenderedReactComponent } from '../src/serverRenderReactComponent'; in node_package/tests/streamServerRenderedReactComponent.test.jsx → import streamServerRenderedReactComponent from '../src/streamServerRenderedReactComponent'; in node_package/tests/streamServerRenderedReactComponent.test.jsx
  """

---

spec/dummy/config/webpack/alias.js:
"""

AI-generated summary of changes

The diff shows the removal of the alias mapping for stream in the Webpack configuration file located at spec/dummy/config/webpack/alias.js. Specifically, the line stream: 'stream-browserify', has been deleted from the alias object within the resolve configuration. This change indicates that the alias for stream which previously redirected to the stream-browserify package is no longer present, potentially affecting how modules that rely on this alias will resolve during the build process.

Alterations to the declarations of exported or public entities

• Alias removed: stream: 'stream-browserify' in the alias object of the Webpack configuration in spec/dummy/config/webpack/alias.js
  """

---

spec/dummy/config/webpack/webpackConfig.js:
"""

AI-generated summary of changes

The diff shows the removal of a line that sets a fallback for the stream module in the clientConfig object within the webpackConfig function. Specifically, the line clientConfig.resolve.fallback = { stream: require.resolve('stream-browserify') }; has been deleted. This change eliminates the configuration that allows the stream module to be resolved using the stream-browserify package, which may affect how the client-side code handles stream functionalities. The rest of the function remains unchanged, including the handling of environment-specific configurations and the logic for determining which webpack configuration to return based on the environment variables.

Alterations to the declarations of exported or public entities

• No alterations to the declarations of exported or public entities were made in this diff.
  """

---

node_package/src/ReactOnRails.node.ts:
"""

AI-generated summary of changes

The changes introduce a new import of the streamServerRenderedReactComponent from the streamServerRenderedReactComponent module into the ReactOnRails.node.ts file. The streamServerRenderedReactComponent is then assigned as a property of the ReactOnRails object. Additionally, the file exports all entities from the ReactOnRails module and sets the default export to the ReactOnRails module as well. This allows for the integration of server-rendered React components into the existing ReactOnRails functionality while maintaining the original exports.

Alterations to the declarations of exported or public entities

• Property added: streamServerRenderedReactComponent in object ReactOnRails in node_package/src/ReactOnRails.node.ts
• Exported all entities: export * from './ReactOnRails'; in node_package/src/ReactOnRails.node.ts
• Default export updated: export { default } from './ReactOnRails'; in node_package/src/ReactOnRails.node.ts
  """

---

package.json:
"""

AI-generated summary of changes

The package.json file has undergone a significant modification in the way the main entry point is defined. The previous single entry point specified by the "main" field has been replaced with an "exports" field that provides a more structured way to define module exports. The new "exports" field specifies two different entry points: one for Node.js environments ("node": "./node_package/lib/ReactOnRails.node.js") and a default entry point for other environments ("default": "./node_package/lib/ReactOnRails.js"). This change enhances the module's compatibility with different environments by allowing for environment-specific entry points.

Additionally, the "main" field has been removed entirely, indicating a shift towards using the "exports" field as the primary means of defining module entry points. This change may affect how consumers of the package import it, as they will now need to rely on the new structure provided by the "exports" field.

Overall, the changes reflect a move towards a more modern module resolution strategy, allowing for better control over how the package is consumed in various JavaScript environments.

Alterations to the declarations of exported or public entities

• Field removed: "main": "node_package/lib/ReactOnRails.js" in package.json
• Field added: "exports": { ... } in package.json
  """

---

spec/dummy/package.json:
"""

AI-generated summary of changes

The diff shows modifications to the package.json file for the react_on_rails project. The primary changes involve the dependency declaration for react-on-rails, which has been altered from a file reference to a link reference. Specifically, the line:

• "react-on-rails": "file:.yalc/react-on-rails",

has been changed to:

• "react-on-rails": "link:.yalc/react-on-rails",

This change indicates a shift in how the react-on-rails package is referenced, moving from a local file system reference to a symbolic link reference, which may affect how the package is resolved during development.

Additionally, several script entries have been modified. The script:

• "yalc-postinstall": "yalc link react-on-rails",

has been replaced with:

• "preinstall": "yarn run link-source && yalc add --link react-on-rails",

and a new script has been added:

• "link-source": "cd ../.. && yarn run build && yalc publish",

These changes suggest a restructuring of the installation process, where the linking of the react-on-rails package is now handled during the pre-installation phase, and a new script is introduced to build and publish the package before linking.

Furthermore, the build:dev script has been modified by removing the --watch flag:

• "build:dev": "rm -rf public/webpack/development && yarn build:rescript && RAILS_ENV=development NODE_ENV=development bin/shakapacker --watch",

to:

• "build:dev": "rm -rf public/webpack/development && yarn build:rescript && RAILS_ENV=development NODE_ENV=development bin/shakapacker",

This change alters the behavior of the development build process, indicating that it will no longer run in watch mode.

Overall, the changes reflect a shift in package linking and script execution strategies within the project.

Alterations to the declarations of exported or public entities

• Dependency updated: "react-on-rails": "file:.yalc/react-on-rails" in spec/dummy/package.json → "react-on-rails": "link:.yalc/react-on-rails" in spec/dummy/package.json
• Script added: "link-source": "cd ../.. && yarn run build && yalc publish" in spec/dummy/package.json
• Script updated: "yalc-postinstall": "yalc link react-on-rails" in spec/dummy/package.json → "preinstall": "yarn run link-source && yalc add --link react-on-rails" in spec/dummy/package.json
• Script updated: "build:dev": "rm -rf public/webpack/development && yarn build:rescript && RAILS_ENV=development NODE_ENV=development bin/shakapacker --watch" in spec/dummy/package.json → "build:dev": "rm -rf public/webpack/development && yarn build:rescript && RAILS_ENV=development NODE_ENV=development bin/shakapacker" in spec/dummy/package.json
  """
  Migrate to react on rails auto-registration react-webpack-rails-tutorial#649 - Migrate to react on rails auto-registration [merged] | .gitignore:
  """

AI-generated summary of changes

• Updates .gitignore to replace the removal of the client/app/generated/ path with a broader pattern and a new header:
  • Replaces the former comment and path:
    • Removes the lines:
      • Generated files
      • /client/app/generated/
  • Adds a new header and ignore patterns:

    • Generated React on Rails packs

    • /generated/
    • .claude/
  • Keeps the existing ignore of /ssr-generated/ and the already-present patterns for React on Rails packs, while broadening generation ignore to any generated directory and introducing a claude directory ignore.

Alterations to the declarations of exported or public entities

• None
  """

---

app/views/layouts/application.html.erb:
"""

AI-generated summary of changes

• Replaced client-bundle asset tags with Stimulus-related asset helpers: removed stylesheet_pack_tag('client-bundle', media: 'all', 'data-turbolinks-track': true) and javascript_pack_tag('client-bundle', 'data-turbolinks-track': true, defer: true); added append_stylesheet_pack_tag('stimulus-bundle'), append_javascript_pack_tag('stimulus-bundle'), and append_javascript_pack_tag('stores-registration').
• Added standalone stylesheet_pack_tag and javascript_pack_tag in the footer: stylesheet_pack_tag(media: 'all', 'data-turbolinks-track': true) and javascript_pack_tag('data-turbolinks-track': true, defer: true).
• Retained Redux store hydration placeholder and ReactOnRails hydration mechanism; no changes to CSRF tags or the hydration placeholder placement beyond asset insertion points.
• In footer, moved hydration placeholder to remain after asset tags; maintains redux_store_hydration_data as the store hydration data.

Alterations to the declarations of exported or public entities

• None
  """

---

app/views/layouts/stimulus_layout.html.erb:
"""

AI-generated summary of changes

• Minor formatting change: a trailing newline added after the closing tag in app/views/layouts/stimulus_layout.html.erb. No changes to head includes, body content, or behavior.

Alterations to the declarations of exported or public entities

• None
  """

---

client/app/bundles/comments/components/SimpleCommentScreen/ror_components/SimpleCommentScreen.jsx:
"""

AI-generated summary of changes

• Updated import paths for CommentForm and CommentList from one level up to two levels up; updated CSS module import path from current directory to one level up. No functional changes to component logic; only module resolution paths are updated.

Alterations to the declarations of exported or public entities

• No changes to exported/public entity signatures.

Estimated code review effort: Medium

Estimated code review effort: Medium
"""

---

client/app/bundles/comments/rescript/RescriptShow/ror_components/RescriptShow.jsx:
"""

AI-generated summary of changes

Adds a new ReScript-generated React component at client/app/bundles/comments/rescript/RescriptShow/ror_components/RescriptShow.jsx. Implements a reducer that returns FetchError when action is not an object, otherwise yields CommentsFetched with the action payload. Introduces ReScriptShow$default using useReducer with initial state commentsFetchStatus as CommentsFetched([]). Adds fetchData to fetch comments via Actions.Fetch.fetchComments, dispatching SetComments on Ok or SetFetchError otherwise. Subscribes to a CommentsChannel via ActionCable, handling connected, received (dispatching SetComments with the incoming data wrapped in an array), and disconnected. Uses two useEffect hooks: one for channel subscription lifecycle, one to trigger fetchData on mount. Renders a header area with a react_on_rails link, a “Comments” section, a CommentForm wired to fetchData, and either an AlertError or CommentList depending on fetch state. Exports reducer as a named export and default as ReScriptShow$default (aliased to default export).

Alterations to the declarations of exported or public entities

• Function added: reducer(param, action) in module client/app/bundles/comments/rescript/RescriptShow/ror_components/RescriptShow.jsx
• Public export added: default (alias of ReScriptShow$default) in module client/app/bundles/comments/rescript/RescriptShow/ror_components/RescriptShow.jsx
  """

---

client/app/bundles/comments/startup/App/ror_components/App.jsx:
"""

AI-generated summary of changes

• Updated import path for NonRouterCommentsContainer in App.jsx: from '../containers/NonRouterCommentsContainer.jsx' to '../../../containers/NonRouterCommentsContainer.jsx'. All other code remains unchanged.

Alterations to the declarations of exported or public entities

• No changes to exported or public declarations.

Estimated code review effort: Medium

Estimated code review effort: Medium

Estimated code review effort: Medium
"""

---

client/app/bundles/comments/startup/NavigationBarApp/ror_components/NavigationBarApp.jsx:
"""

AI-generated summary of changes

• Imports were moved from shallow relative paths to deeper relative paths in NavigationBarApp.jsx:
  • NavigationBar, NavigationBarContainer, and paths imports now resolve via ../../../components/NavigationBar/NavigationBar.jsx, ../../../containers/NavigationBarContainer.jsx, and ../../../constants/paths respectively.
    This changes only module resolution; no functional logic or public exports are altered.

Alterations to the declarations of exported or public entities

• No changes to declarations of exported/public entities.

Estimated code review effort: Low
"""

---

client/app/bundles/comments/startup/RouterApp/ror_components/RouterApp.client.jsx:
"""

AI-generated summary of changes

• Updated RouterApp.client.jsx comment to reference RouterApp.server.jsx instead of ServerRouterApp.jsx, and changed routes import from '../routes/routes.jsx' to '../../../routes/routes.jsx', without changing runtime logic or control flow.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium
"""

---

client/app/bundles/comments/startup/RouterApp/ror_components/RouterApp.server.jsx:
"""

AI-generated summary of changes

• Updated comments to reflect new comparison target: from // Compare to ../ClientRouterApp.jsx to // Compare to ./RouterApp.client.jsx.
• Updated route import path: from '../routes/routes.jsx' to '../../../routes/routes.jsx'.

Alterations to the declarations of exported or public entities

• No changes to exported or public entity declarations.

Estimated code review effort: Medium
"""

---

client/app/packs/client-bundle.js:
"""

AI-generated summary of changes

Deleted the client/app/packs/client-bundle.js file, which previously bootstrapped the ReactOnRails client integration. It imported ReactOnRails, jQuery exposure, jquery-ujs, and application styles, and it imported UI components (App, RouterApp, NavigationBarApp, SimpleCommentScreen, Footer, RescriptShow) as well as stores (routerCommentsStore, commentsStore). It configured ReactOnRails.setOptions with traceTurbolinks: true, registered components via ReactOnRails.register, and registered stores with ReactOnRails.registerStore. Removing this file eliminates all of these bootstrapping imports and registrations, i.e., the client-side ReactOnRails bootstrap and related UI registrations.

• None

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium
"""

---

client/app/packs/server-bundle.js:
"""

AI-generated summary of changes

• Replaced full ReactOnRails initialization and explicit component/store registrations with a minimal setup: added an import for stores-registration and replaced the large registration blocks with a single import of the generated server bundle. The code now imports "./../generated/server-bundle-generated.js" and includes a comment indicating it was added by the generate_packs task.
• Removed registrations for App, RouterApp, NavigationBarApp, SimpleCommentScreen, Footer, and RescriptShow, as well as registration of routerCommentsStore and commentsStore.
• Added a comment line noting the import was added by react_on_rails:generate_packs rake task.

Alterations to the declarations of exported or public entities

• No changes to exported/public entity declarations.

major_updates

Estimated code review effort: Medium
"""

---

client/app/packs/stimulus-bundle.js:
"""

AI-generated summary of changes

Removed manual component registrations by deleting imports of NavigationBarApp and Footer and the ReactOnRails.register block. Replaced with comments indicating components are auto-registered via ror_components directories, implying no manual registration code remains. Other initialization code (imports and Turbo options) remains unchanged. Observed behavior change: explicit registration of components is eliminated; components will be registered automatically through the new approach.

Alterations to the declarations of exported or public entities

• No changes to exported/public declarations.

Estimated code review effort: Medium
"""

---

client/app/packs/stores-registration.js:
"""

AI-generated summary of changes

• Adds new file client/app/packs/stores-registration.js that imports ReactOnRails and two stores (routerCommentsStore and commentsStore) and registers them via ReactOnRails.registerStore with an object containing the two stores. Includes a comment noting that stores must be manually registered since they're not components.

Alterations to the declarations of exported or public entities

• No exported/public entity signature changes in this diff.

Estimated code review effort: Medium
"""

---

config/initializers/react_on_rails.rb:
"""

AI-generated summary of changes

• Replaced removal of webpack_generated_files check with new auto-registration configuration for v16.
• Added two new configuration options: config.components_subdirectory set to "ror_components" and config.auto_load_bundle set to true.
• Retains existing test/production build commands and other existing configuration options.
  """

---

config/shakapacker.yml:
"""

AI-generated summary of changes

Adds a new configuration key nested_entries: true under the default Shakapacker settings in config/shakapacker.yml. This is the sole modification; no lines were removed or altered besides the addition. It enables nested entries in the config.

Alterations to the declarations of exported or public entities

• No exported/public entity declarations modified.
  """

---

.github/workflows/js_test.yml:
"""

AI-generated summary of changes

• Adds a new CI step "Generate React on Rails packs" to the JS CI workflow, executing bundle exec rails react_on_rails:generate_packs after the "Build i18n libraries" step and before "Run js tests". No other changes to logic or flow.

• No changes to exported/public entity declarations.

Estimated code review effort: Medium

Alterations to the declarations of exported or public entities

• No exported/public entity declarations modified.

Estimated code review effort: Medium
"""

---

.github/workflows/lint_test.yml:
"""

AI-generated summary of changes

Adds a new CI step "Generate React on Rails packs" to the lint_test.yml workflow. This step is inserted after "Build i18n libraries" and before "Run lint", executing the command "bundle exec rails react_on_rails:generate_packs". No other behavioral changes.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium
"""

---

.github/workflows/rspec_test.yml:
"""

AI-generated summary of changes

Adds a new workflow step in .github/workflows/rspec_test.yml under the test job steps: a step named “Generate React on Rails packs” that runs the command bundle exec rails react_on_rails:generate_packs. This step is inserted after the existing “Build i18n libraries” step and before the subsequent “Build Rescript components” step. No deletions or other changes to existing steps.

Alterations to the declarations of exported or public entities

• Step added: In file .github/workflows/rspec_test.yml, under the test job steps, added:
  • name: Generate React on Rails packs
  • run: bundle exec rails react_on_rails:generate_packs

Estimated code review effort: Medium
"""

---

client/app/bundles/comments/startup/serverRegistration.jsx:
"""

AI-generated summary of changes

• Updated import paths for components to their ror_components subdirectories:
  • App from ./App to ./App/ror_components/App
  • RouterApp from ./ServerRouterApp to ./RouterApp/ror_components/RouterApp.server
  • SimpleCommentScreen from ../components/SimpleCommentScreen/SimpleCommentScreen to ../components/SimpleCommentScreen/ror_components/SimpleCommentScreen
  • NavigationBarApp from ./NavigationBarApp to ./NavigationBarApp/ror_components/NavigationBarApp
  • Footer from ../components/Footer/Footer to ../components/Footer/ror_components/Footer
• ReactOnRails.register now includes RouterApp, NavigationBarApp, SimpleCommentScreen, and Footer in addition to App.
• ReactOnRails.registerStore block remains unchanged.

Alterations to the declarations of exported or public entities

• No changes to signatures of exported/public entities.

Estimated code review effort: Medium
"""

---

TODO_TURBO_WARNING.md:
"""

AI-generated summary of changes

Adds a new Markdown file TODO_TURBO_WARNING.md that documents a console warning when Turbo is loaded from the body rather than the head. Describes the root causes across Turbo, Shakapacker, and React on Rails integration, lists attempted solutions that failed, outlines potential future approaches, and states the current working condition (warnings are cosmetic and the app functions with tags at end of body). Includes references to related PRs and docs. No executable code or logic changes are introduced.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Medium
"""

---

Procfile.dev:
"""

AI-generated summary of changes

• Updated Procfile.dev entry for Rails server from running via direct bin/rails to using bundle exec rails s, preserving port 3000. No change to other entries. Control flow unchanged; only how Rails is invoked is altered.

Estimated code review effort: Medium
"""
shakacode/react_on_rails#1889 - Prepare for removing react server dom from the RSC bundle [merged] | packages/react-on-rails-pro/src/ReactOnRailsRSC.ts:
"""

AI-generated summary of changes

Changed the import source for three re-exports from './streamServerRenderedReactComponent.ts' to './streamingUtils.ts', altering the module path without changing export names or behavior. No other logic or control-flow changes are present.

• No changes to exported/public entity signatures.

Estimated code review effort: Medium
"""

---

packages/react-on-rails-pro/src/streamServerRenderedReactComponent.ts:
"""

AI-generated summary of changes

• Replaced a large, multi-piece streaming implementation with a leaner approach that delegates core streaming orchestration to streamingUtils.ts. Removed direct dependencies on React server render utilities, console replay, and per-request trackers.
• Introduced a new internal streamRenderReactComponent that uses renderToPipeableStream and streams payloads via a dedicated transformation pipeline (transformRenderStreamChunksToResultObject) and injections (injectRSCPayload) while maintaining error handling and shell readiness semantics.
• Retired previously exported complex types and trackers (StreamRenderer, StreamingTrackers, and streamServerRenderedComponent) from this module; replaced with a streamlined internal wiring that relies on external streaming utilities.
• Public API remains the default export streamServerRenderedReactComponent, but its internal implementation now composes via streamRenderReactComponent and a generic streamServerRenderedComponent from streamingUtils.ts, reducing local coupling and complexity.
• Updated imports to reflect the new streaming utilities module and removed unused/renamed imports (e.g., React server rendering helpers, bufferStream, and legacy error handling helpers).

Alterations to the declarations of exported or public entities

• Removed: export type StreamingTrackers from this module.
• Removed: export const streamServerRenderedComponent (the per-request tracker container) from this module.
• Removed: export type StreamRenderer<T, P extends RenderParams> and its associated documentation.
• Public API retained: export default streamServerRenderedReactComponent (signature remains: (options: RenderParams) => Readable).
• Signatures eliminated from local scope (not exported publicly): various internal helper types and functions related to buffering, per-request trackers, and direct stream transformation logic.

Estimated code review effort: Medium
"""

---

packages/react-on-rails-pro/src/streamingUtils.ts:
"""

AI-generated summary of changes

• Introduces a new streaming utilities module (streamingUtils.ts) that provides:
  • A bufferStream function to wrap a Readable and buffer data, error, and end events until reading begins, then replay them in order with proper error propagation. It exposes:
    • stream: a buffered Readable
    • emitError: a function to emit or buffer errors until reading starts
  • A transformRenderStreamChunksToResultObject function that converts render chunks into a JSON result object, including a console replay script, and resets render state after each chunk.
  • A streaming pipeline integration via streamServerRenderedComponent that:
    • Creates per-request PostSSRHookTracker and RSCRequestTracker instances
    • Augments Rails context with streaming capabilities (addPostSSRHook, getRSCPayloadStream)
    • Retrieves and validates a component from a registry, creates a React output, and handles server-rendered streams or promises
    • On errors, constructs an HTML error via handleError, emits the error if allowed, and returns a readable stream containing the error HTML, ensuring proper end/cleanup
  • Includes internal buffering, error handling, and end-of-stream coordination to support streaming SSR in a robust way
• Adds new exported public entities:
  • transformRenderStreamChunksToResultObject(renderState: StreamRenderState)
  • StreamingTrackers type
  • streamServerRenderedComponent<T, P extends RenderParams>(options: P, renderStrategy: StreamRenderer<T, P>): T
• Establishes per-request streaming infrastructure and error-safe streaming for React Server Components in a Rails context.

Alterations to the declarations of exported or public entities

• Method added: export const transformRenderStreamChunksToResultObject(renderState: StreamRenderState) in packages/react-on-rails-pro/src/streamingUtils.ts
• Type added: export type StreamingTrackers in packages/react-on-rails-pro/src/streamingUtils.ts
  • Structure: { postSSRHookTracker: PostSSRHookTracker; rscRequestTracker: RSCRequestTracker; }
• Method added: export const streamServerRenderedComponent<T, P extends RenderParams>(options: P, renderStrategy: StreamRenderer<T, P>): T in packages/react-on-rails-pro/src/streamingUtils.ts

Manifest File Analyzer

Estimated code review effort: High
"""

---

packages/react-on-rails/package.json:
"""

AI-generated summary of changes

In the exports map of packages/react-on-rails/package.json, the public export alias "./handleError" now resolves to "./lib/generateRenderingErrorMessage.js" instead of "./lib/handleError.js". The actual public surface remains the same key "./handleError", but its implementation target is changed, altering the module that is resolved for that export. No other exports or public signatures are modified; control flow and error handling behavior depend on the new module.

• Method signature updated: ./handleError export in packages/react-on-rails/package.json → now aliases to ./lib/generateRenderingErrorMessage.js instead of ./lib/handleError.js

Estimated code review effort: Medium
"""

---

packages/react-on-rails/src/base/full.ts:
"""

AI-generated summary of changes

• Import source of handleError changed from ../handleError.ts to ../generateRenderingErrorMessage.ts in packages/react-on-rails/src/base/full.ts. No other behavior or control flow changes; the handleError function is now resolved from a different module, but its usage remains the same.

• No changes to exported/public declarations (no signature changes to public APIs).

Estimated code review effort: Medium
"""

---

packages/react-on-rails/src/serverRenderReactComponent.ts:
"""

AI-generated summary of changes

• The only observable change is the import source of the handleError alias: from ./handleError.ts to ./generateRenderingErrorMessage.ts. The exported symbol name (handleError) remains the same and usage is unchanged; no functional logic or control flow changes are introduced beyond the module boundary.

Alterations to the declarations of exported or public entities

• No changes to exported/public entity signatures.

Manifest File Analyzer

Estimated code review effort: Medium
"""
shakacode/react_on_rails#2015 - Concurrently drain streaming fibers [merged] | react_on_rails_pro/CHANGELOG.md:
"""

AI-generated summary of changes

• Adds two new Unreleased sections: Improved and Added.
• Improved: introduces concurrent processing for streaming React components to replace sequential processing, reducing latency for stream_view_containing_react_components.
• Added: introduces config.concurrent_component_streaming_buffer_size with default 64 to tune memory buffer for concurrent streaming (trade-off between memory usage and performance).
• Added: adds async gem dependency (>= 2.6) to support the new concurrent streaming feature.

"""

---

react_on_rails_pro/lib/react_on_rails_pro/concerns/stream.rb:
"""

AI-generated summary of changes

• Replaces the direct iterative draining of fibers with a concurrent streaming model using Async and a LimitedQueue.
• Introduces drain_streams_concurrently to coordinate producer tasks (build_producer_tasks) and a writer task (build_writer_task) that dequeues chunks and writes them in order.
• Adds memory-bounded buffering via a queue; producers enqueue [index, chunk], writer dequeues and writes, and the queue is closed to signal end-of-stream.
• Moves stream finalization to an ensure block that closes the stream after draining, instead of closing inside the original loop.
• Replaces the in-loop fiber.resume iteration with a multi-task flow: starts producers and writer, waits on producers, then signals end-of-stream and waits for writer.
• Adds private helper methods for building producer tasks and the writer task; each producer resumes fibers and enqueues chunks with their index.
• Introduces explicit end-of-stream signaling via queue.close and handling of nil dequeues by the writer.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: High

Estimated code review effort: High
"""

---

react_on_rails_pro/lib/react_on_rails_pro/configuration.rb:
"""

AI-generated summary of changes

• Adds a new configuration option concurrent_component_streaming_buffer_size with a default value of 64.
• Exposes concurrent_component_streaming_buffer_size as a public attribute on the Configuration class.
• Extends the Configuration initializer to accept concurrent_component_streaming_buffer_size and stores it on the instance.
• Includes concurrent_component_streaming_buffer_size in the public configuration hash produced by ReactOnRailsPro.configuration.
• Wires concurrent_component_streaming_buffer_size into the initial Configuration.new(...) call.
• Introduces a public method validate_concurrent_component_streaming_buffer_size to enforce that concurrent_component_streaming_buffer_size is a positive numeric value.
• Invokes validate_concurrent_component_streaming_buffer_size during setup_config_values.

Alterations to the declarations of exported or public entities

• Constant added: DEFAULT_CONCURRENT_COMPONENT_STREAMING_BUFFER_SIZE = 64 in class ReactOnRailsPro::Configuration
• Attribute accessor updated: :concurrent_component_streaming_buffer_size in ReactOnRailsPro::Configuration
• Constructor signature updated: include concurrent_component_streaming_buffer_size: in def initialize(...)
• Initialization assignment updated: self.concurrent_component_streaming_buffer_size = concurrent_component_streaming_buffer_size in ReactOnRailsPro::Configuration#initialize
• Public API change: concurrent_component_streaming_buffer_size appears in the configuration hash returned by ReactOnRailsPro.configuration
• Wiring change: pass concurrent_component_streaming_buffer_size in the initial Configuration.new(...) call
• Public method added: validate_concurrent_component_streaming_buffer_size in ReactOnRailsPro::Configuration to validate the new setting
• Validation invocation: call to validate_concurrent_component_streaming_buffer_size inside setup_config_values

Manifest File Analyzer

Estimated code review effort: Medium
"""

---

react_on_rails_pro/lib/react_on_rails_pro/utils.rb:
"""

AI-generated summary of changes

• Updated inline documentation to refer to Shakapacker instead of Webpacker for two methods.
• bundle_file_name now uses ReactOnRails::PackerUtils.bundle_js_uri_from_packer to obtain the path and Pathname.basename for the file name, replacing the previous webpacker-based semantics.
• server_bundle_file_name signature remains unchanged, but its implementation shifts from deriving a hash via a simple wrapper around bundle_file_name to caching via an instance variable and computing the server bundle name through bundle_file_name, centralizing the name resolution.
• Updated comments to reflect “Shakapacker” usage and clarified the purpose of keys (cache keys vs fragment-caching keys) accordingly.
• No observable changes to return values or control flow aside from the moved/renamed processing path and updated comments.

Alterations to the declarations of exported or public entities

• No signature changes detected in exported/public entities.

Estimated code review effort: Medium
"""

---

react_on_rails_pro/react_on_rails_pro.gemspec:
"""

AI-generated summary of changes

Adds a new runtime dependency "async" with version constraint ">= 2.6" to the gemspec, increasing runtime requirements. No other dependencies or metadata are modified; the change is a single addition to s.add_runtime_dependency.

• Method added: s.add_runtime_dependency "async", ">= 2.6" in file react_on_rails_pro/react_on_rails_pro.gemspec

Estimated code review effort: Medium
"""

---

react_on_rails_pro/spec/dummy/spec/helpers/react_on_rails_pro_helper_spec.rb:
"""

AI-generated summary of changes

• Adds Async::Queue-based streaming support to tests by allowing mock_request_and_response to handle both Async::Queue and Array inputs. When a queue is provided, chunks are dequeued in a loop until nil and yielded as before; when an array is provided, behavior remains unchanged.
• Introduces execute_stream_view_containing_react_components as a new test helper that wires an Async queue to mock_request_and_response, drives the streaming flow via stream_view_containing_react_components, enqueues chunks progressively with delays, and asserts that written chunks mirror received chunks during streaming.
• Replaces direct invocations of stream_view_containing_react_components(template: ...) with the new execute_stream_view_containing_react_components helper in multiple tests to drive the Async-based path.
• Extends the stream_view_containing_react_components describe block to use Async::Queue-driven mocks, mirroring the same async-chunk delivery behavior used for streaming tests.
• Keeps existing assertions around chunk writing timing, Rails context and component tagging, and content checks, but adapts control flow to support both synchronous array inputs and asynchronous queue inputs.
• Adds require statements for async and async/queue to enable new Async-based test paths.

Alterations to the declarations of exported or public entities

• None

Estimated code review effort: Major
"""

---

react_on_rails_pro/spec/react_on_rails_pro/stream_spec.rb:
"""

AI-generated summary of changes

• Adds a new StreamController class inside react_on_rails_pro/spec/react_on_rails_pro/stream_spec.rb that includes ReactOnRailsPro::Stream, exposes a public response reader, and implements initialize(component_queues:, initial_response: "TEMPLATE") and render_to_string(**_opts). The render_to_string method sets up per-queue Fibers to yield chunks from Async::Queue instances and returns the initial_response.
• Extends tests with a new "Component streaming concurrency" suite, introducing helpers run_stream and setup_stream_test. The setup mocks ActionController::Live::Response and Buffer, wires controller.response to the mocked response, and configures stream.write/close expectations.
• Adds test scenarios for concurrent streaming, per-component ordering, empty component lists, single components, and backpressure with a slow writer, including assertions on interleaving and timing.
• Duplicates or augments streaming tests across sections to reinforce concurrency behavior and cleanup paths.
• Introduces backpressure and disconnect-handling logic in tests by simulating slow writes and observing write timings and closures.

Alterations to the declarations of exported or public entities

• New class added: StreamController in react_on_rails_pro/spec/react_on_rails_pro/stream_spec.rb
• Public module include added to the new class: include ReactOnRailsPro::Stream
• Public attribute reader added: attr_reader :response in StreamController
• Public method added: def initialize(component_queues:, initial_response: "TEMPLATE") in StreamController
• Public method added: def render_to_string(**_opts) in StreamController
• Public attribute and parameter usage: @component_queues, @initial_response in StreamController initialization
• New test helper methods and test-scoped public-like constructs introduced within the spec (e.g., run_stream, setup_stream_test) to drive public-facing streaming behavior tests
  """
  Replace manual Fibers with Async gem primitives for component streaming react_on_rails#2111 - Replace manual Fibers with Async gem primitives for component streaming [merged] | react_on_rails_pro/app/helpers/react_on_rails_pro_helper.rb:
  """

AI-generated summary of changes

• Introduces on_complete callback support for streaming:
  • stream_react_component and rsc_payload_react_component now extract on_complete from options and invoke a new consumer_stream_async(on_complete: on_complete) wrapper around the existing streaming logic.
  • New consumer_stream_async(on_complete:) responsible for coordinating asynchronous streaming via a barrier, buffering, and returning the first chunk synchronously while enqueuing subsequent chunks to the main output; collects all chunks when on_complete is provided and invokes the callback upon completion.
  • Replaces the previous run_stream_inside_fiber flow with barrier-based streaming: first chunk returned synchronously, later chunks delivered through the main output queue; remaining chunks collected and delivered via on_complete(all_chunks) if provided.
  • In handle_stream_cache_hit, enqueues rest_chunks asynchronously via the barrier instead of yielding within a fiber; returns the initial chunk directly.
  • In handle_stream_cache_miss, builds cache_aware_options with on_complete: lambda { |chunks| Rails.cache.write(...) } and delegates to render_stream_component_with_props, removing the fiber-based wrapper logic.
  • render_stream_component_with_props path remains but now supports the new on_complete mechanism and barrier coordination.
• Public API influence:
  • Streaming helpers now accept an optional on_complete callback to enable post-stream caching and barrier-based buffering.
• Caching integration:
  • Cache hit path writes remaining chunks to the barrier queue; miss path uses on_complete to persist chunks to cache after streaming.
• Control flow shift:
  • From fiber-centric streaming to barrier-based asynchronous streaming with a synchronous first chunk return and callback-based buffering.

Alterations to the declarations of exported or public entities

• Method signature updated: def stream_react_component(component_name, options = {}) → now extracts on_complete from options and calls consumer_stream_async(on_complete: on_complete) around the existing streaming logic.
• Method signature updated: def rsc_payload_react_component(component_name, options = {}) → now extracts on_complete from options and calls consumer_stream_async(on_complete: on_complete) around the existing streaming logic.
• Method added: def consumer_stream_async(on_complete:) in react_on_rails_pro/app/helpers/react_on_rails_pro_helper.rb with new barrier-based streaming implementation, first-chunk synchronous return via an async variable, optional collection of all chunks, and invocation of the on_complete callback upon completion.

Estimated code review effort: High

"""

---

react_on_rails_pro/lib/react_on_rails_pro/concerns/stream.rb:
"""

AI-generated summary of changes

• Replaces per-fiber producer/writer streaming with a barrier-based drain model. Introduces Async::Barrier and a main output queue; renders the template string earlier and writes to the response stream upfront, then drains via a dedicated drain_streams_concurrently path coordinated by the barrier. Removes previous private drain helper and producer/writer task methods; moves drain logic into a consolidated drain operation that waits on the barrier and closes the stream after draining. Adjusts control flow so the response stream is not closed in an ensure block, and ensures end-of-stream signaling is performed after draining.

Alterations to the declarations of exported or public entities

• None

Manifest File Analyzer

"""

---

react_on_rails_pro/spec/react_on_rails_pro/stream_spec.rb:
"""

AI-generated summary of changes

• Replaces Fiber-based streaming with an async barrier-based flow: iterates component queues, starts an async task via @async_barrier.async, dequeues chunks, and enqueues them into @main_output_queue instead of yielding chunks via Fiber.yield. Adds require "async/variable". Comments indicate testing enqueues all chunks and that first chunks are part of template HTML. Public method render_to_string signature remains unchanged and still returns @initial_response. Changes affect control flow from yielding to enqueuing and introduce asynchronous task creation per queue.

Alterations to the declarations of exported or public entities

• None
  """

---

react_on_rails_pro/spec/dummy/spec/helpers/react_on_rails_pro_helper_spec.rb:
"""

AI-generated summary of changes

• Replaces fiber-based streaming coordination with Async::Barrier and Async::Queue primitives in tests.
• Wraps test contexts in Sync blocks to establish an async lifecycle, initializing @async_barrier and @main_output_queue per test scope.
• stream_react_component tests transition from resuming fibers to streaming chunks via the output queue; initial chunk remains synchronous, subsequent chunks are consumed from the queue after barrier synchronization.
• Adjusts assertions to reflect async chunk collection: initial chunk present synchronously; remaining chunks collected from the queue after barrier wait and queue draining.
• Updates related streaming helpers (render_cached_random_value, attribution tests) to initialize Async primitives and run through an explicit async lifecycle, ensuring consistent cache and streaming behavior.
• Reworks tests to drain and inspect Async::Queue outputs for subsequent chunks instead of direct fiber resumes.
• Introduces around hooks to establish async context across multiple sections and enables rubocop pragmas accordingly.
• Minor structural/test-scoping changes to reflect the new async streaming model (e.g., “streams subsequent chunks to the output queue,” “collect remaining chunks from queue”).
• Adds require "async/barrier" and activates async scaffolding in several test scopes, including stream_react_component, cached streaming helpers, and attribution-related tests.

Alterations to the declarations of exported or public entities

• No changes to exported/public entity declarations detected.

Manifest File Analyzer

Update scope tag

"""

👤 Suggested Assignees

• justin808
• ihabadham
• AbanoubGhadban
• alexeyr-ci
• Judahmeek

---

🧪 Issue enrichment is currently in early access.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false