react_on_rails_pro 16.2.0.beta.20 → 16.2.0.rc.0

data/docs/react-server-components/server-side-rendering.md

@@ -1,6 +1,7 @@
 # SSR React Server Components
 
 Before reading this document, please read:
+
 1. [Create React Server Component without SSR](./create-without-ssr.md)
 2. [Add Streaming and Interactivity to RSC Page](./add-streaming-and-interactivity.md)
 
@@ -13,7 +14,7 @@ Let's make React on Rails server-side render the React Server Component Page we
 Update the `react_server_component_without_ssr.html.erb` view to pass `prerender: true` to the `react_component` helper.
 
 ```erb
-<%= react_component("ReactServerComponentPage", 
+<%= react_component("ReactServerComponentPage",
     prerender: true,
     trace: true,
     id: "ReactServerComponentPage-react-component-0") %>
@@ -37,33 +38,33 @@ To enable streaming SSR for React Server Components, we need to:
 
 1. Create a new view called `react_server_component_ssr.html.erb` with the following content:
 
-    ```erb
-    # app/views/pages/react_server_component_ssr.html.erb
-    <%= stream_react_component("ReactServerComponentPage",
-        id: "ReactServerComponentPage-react-component-0") %>
-    
-    <h1>React Server Component with SSR</h1>
-    ```
+   ```erb
+   # app/views/pages/react_server_component_ssr.html.erb
+   <%= stream_react_component("ReactServerComponentPage",
+       id: "ReactServerComponentPage-react-component-0") %>
+
+   <h1>React Server Component with SSR</h1>
+   ```
 
 2. Ensure our controller includes `ReactOnRailsPro::Stream` and use the `stream_view_containing_react_components` helper to render the view:
 
-    ```ruby
-    # app/controllers/pages_controller.rb
-    class PagesController < ApplicationController
-      include ReactOnRailsPro::Stream
-    
-      def react_server_component_ssr
-        stream_view_containing_react_components(template: "pages/react_server_component_ssr")
-      end
-    end
-    ```
+   ```ruby
+   # app/controllers/pages_controller.rb
+   class PagesController < ApplicationController
+     include ReactOnRailsPro::Stream
+
+     def react_server_component_ssr
+       stream_view_containing_react_components(template: "pages/react_server_component_ssr")
+     end
+   end
+   ```
 
 3. Add the route to `config/routes.rb`:
 
-    ```ruby
-    # config/routes.rb
-    get "/react_server_component_ssr", to: "pages#react_server_component_ssr"
-    ```
+   ```ruby
+   # config/routes.rb
+   get "/react_server_component_ssr", to: "pages#react_server_component_ssr"
+   ```
 
 Now, when you visit the page, you should see the entire React Server Component page rendered in the browser. And if you viewed the page source, you should see the HTML being streamed to the browser.
 

data/docs/release-notes/4.0.md

@@ -1,94 +1,103 @@
-# 4.0 Release Notes
-
-## 🚀 Major New Features
-
-### React Server Components (RSC) - Full Production Support
-React on Rails Pro now provides comprehensive support for React Server Components, enabling you to build the next generation of React applications:
-
-- **Full RSC Integration**: Seamlessly use React Server Components in your Rails apps with zero configuration
-- **Bundle Optimization**: Automatic client/server code splitting that significantly reduces client-side JavaScript
-- **Server-Side Data Fetching**: Direct access to databases, APIs, and server resources from React components
-- **Progressive Hydration**: Client components hydrate independently for optimal performance
-- **RSC Payload Streaming**: Efficient streaming of component data with embedded payloads
-- **Compatible with React Router**: [Use React Router with RSC](../react-server-components/inside-client-components.md)
-
-See our [complete RSC tutorial](../react-server-components-tutorial.md) to get started.
-
-### Advanced Streaming Server Rendering
-Building on React 19's streaming capabilities, React on Rails Pro delivers:
-
-- **Progressive HTML Streaming**: Send page content as it becomes available
-- **Suspense Boundary Support**: Handle async components with proper loading states
-- **Selective Hydration**: Components become interactive as soon as they're ready
-- **Error Boundary Handling**: Graceful error handling during streaming with configurable error raising
-- **Async Console Log Replay**: Debug async server-side rendering with client-side console output
-
-### Enhanced Error Reporting & Tracing
-Completely redesigned error reporting system with:
-
-- **Custom Integration Support**: Integrate with any error reporting service (Sentry, Honeybadger, or custom)
-- **Sentry SDK v8 Support**: Latest Sentry integration with improved performance
-- **Flexible Configuration**: Configure error reporting according to your preferences
-- **Enhanced Tracing**: Better visibility into rendering performance and issues
-
-## Performance Improvements
-
-### Node Renderer Architecture
-- **Fastify 5 Integration**: Upgraded from Express to Fastify for significantly better performance
-- **HTTP/2 Cleartext Communication**: Rails communicates with Node renderer over HTTP/2 instead of HTTP/1.1
-- **HTTPX Client**: Replaced Net::HTTP with HTTPX for improved connection handling
-- **Pino Logging**: Switched from Winston to Pino for better performance and Fastify compatibility
-
-These changes provide:
-- Better performance when Node renderer is deployed on the same machine as Rails
-- Significantly improved performance when deployed in separate workloads
-- Enhanced connection reuse and multiplexing capabilities
-- Better error handling and process management
-
-
-### Changes Specific For RSC Rendering Optimization
-- **Cross-Bundle Communication**: Components can now interact seamlessly across different bundles using the new `runOnOtherBundle` function, enabling advanced composition and modularization patterns.
-- **Single-Pass Server Component Rendering**: Server components are rendered just once within the RSC bundle, then efficiently reused for both SSR and client hydration—eliminating redundant work and improving performance.
-- **Reduced HTTP Requests**: RSC payloads are now embedded directly into the initial HTML response. No need to make an additional request to fetch the RSC payload.
-- **Protocol v2.0 – Unified Bundle Management**: The new protocol allows simultaneous upload of both server and RSC bundles in a single request, supporting multiple bundle uploads and providing robust, flexible bundle management for complex applications.
-
-## Breaking Changes
-
-### Configuration Updates
-- **Sentry/Honeybadger**: Remove old configuration options starting with `sentry` or `honeybadger`
-- **Timer Polyfills**: `includeTimerPolyfills` is renamed to `stubTimers`
-- **Environment Variables**: `RENDERER_STUB_TIMERS` instead of `INCLUDE_TIMER_POLYFILLS`
-- **Error Reporting**: Follow the [Error Reporting and Tracing](../node-renderer/error-reporting-and-tracing.md) documentation for new setup
-
-### Dependency Requirements
-- **Ruby 3+**: Dropped support for Ruby 2.7 (EOL)
-- **React on Rails 15+**: Required for RSC and streaming features
-- **Node 20+**: Strongly recommended (older versions require specific package.json resolutions)
-
-### Package.json Resolutions (for Node < 20)
-If using older Node versions, add to your `package.json`:
-```json
-"resolutions": {
-  "@fastify/formbody": "^7.4.0",
-  "@fastify/multipart": "^8.3.1",
-  "fastify": "^4.29.0"
-}
-```
-
-## Getting Started
-
-- **RSC Tutorial**: [Complete React Server Components Guide](../react-server-components-tutorial.md)
-- **Streaming SSR**: [Streaming Server Rendering Documentation](../streaming-server-rendering.md)
-- **Error Reporting**: [Error Reporting and Tracing Setup](../node-renderer/error-reporting-and-tracing.md)
-- **Performance**: [Caching and Optimization Guide](../caching.md)
-
-## Support & Community
-
-- **Documentation**: Comprehensive guides and tutorials available
-- **Examples**: Working examples in the spec/dummy application
-- **GitHub**: Active development and community support
-- **Discussions**: Join the [React on Rails community](https://forum.shakacode.com/) for help and updates
-
----
-
-*React on Rails Pro 4.0 represents a major evolution in server-side React rendering, bringing React Server Components and advanced streaming to the Rails ecosystem with enterprise-grade performance and reliability.*
+# 4.0 Release Notes
+
+## 🚀 Major New Features
+
+### React Server Components (RSC) - Full Production Support
+
+React on Rails Pro now provides comprehensive support for React Server Components, enabling you to build the next generation of React applications:
+
+- **Full RSC Integration**: Seamlessly use React Server Components in your Rails apps with zero configuration
+- **Bundle Optimization**: Automatic client/server code splitting that significantly reduces client-side JavaScript
+- **Server-Side Data Fetching**: Direct access to databases, APIs, and server resources from React components
+- **Progressive Hydration**: Client components hydrate independently for optimal performance
+- **RSC Payload Streaming**: Efficient streaming of component data with embedded payloads
+- **Compatible with React Router**: [Use React Router with RSC](../react-server-components/inside-client-components.md)
+
+See our [complete RSC tutorial](../react-server-components/tutorial.md) to get started.
+
+### Advanced Streaming Server Rendering
+
+Building on React 19's streaming capabilities, React on Rails Pro delivers:
+
+- **Progressive HTML Streaming**: Send page content as it becomes available
+- **Suspense Boundary Support**: Handle async components with proper loading states
+- **Selective Hydration**: Components become interactive as soon as they're ready
+- **Error Boundary Handling**: Graceful error handling during streaming with configurable error raising
+- **Async Console Log Replay**: Debug async server-side rendering with client-side console output
+
+### Enhanced Error Reporting & Tracing
+
+Completely redesigned error reporting system with:
+
+- **Custom Integration Support**: Integrate with any error reporting service (Sentry, Honeybadger, or custom)
+- **Sentry SDK v8 Support**: Latest Sentry integration with improved performance
+- **Flexible Configuration**: Configure error reporting according to your preferences
+- **Enhanced Tracing**: Better visibility into rendering performance and issues
+
+## Performance Improvements
+
+### Node Renderer Architecture
+
+- **Fastify 5 Integration**: Upgraded from Express to Fastify for significantly better performance
+- **HTTP/2 Cleartext Communication**: Rails communicates with Node renderer over HTTP/2 instead of HTTP/1.1
+- **HTTPX Client**: Replaced Net::HTTP with HTTPX for improved connection handling
+- **Pino Logging**: Switched from Winston to Pino for better performance and Fastify compatibility
+
+These changes provide:
+
+- Better performance when Node renderer is deployed on the same machine as Rails
+- Significantly improved performance when deployed in separate workloads
+- Enhanced connection reuse and multiplexing capabilities
+- Better error handling and process management
+
+### Changes Specific For RSC Rendering Optimization
+
+- **Cross-Bundle Communication**: Components can now interact seamlessly across different bundles using the new `runOnOtherBundle` function, enabling advanced composition and modularization patterns.
+- **Single-Pass Server Component Rendering**: Server components are rendered just once within the RSC bundle, then efficiently reused for both SSR and client hydration—eliminating redundant work and improving performance.
+- **Reduced HTTP Requests**: RSC payloads are now embedded directly into the initial HTML response. No need to make an additional request to fetch the RSC payload.
+- **Protocol v2.0 – Unified Bundle Management**: The new protocol allows simultaneous upload of both server and RSC bundles in a single request, supporting multiple bundle uploads and providing robust, flexible bundle management for complex applications.
+
+## Breaking Changes
+
+### Configuration Updates
+
+- **Sentry/Honeybadger**: Remove old configuration options starting with `sentry` or `honeybadger`
+- **Timer Polyfills**: `includeTimerPolyfills` is renamed to `stubTimers`
+- **Environment Variables**: `RENDERER_STUB_TIMERS` instead of `INCLUDE_TIMER_POLYFILLS`
+- **Error Reporting**: Follow the [Error Reporting and Tracing](../node-renderer/error-reporting-and-tracing.md) documentation for new setup
+
+### Dependency Requirements
+
+- **Ruby 3+**: Dropped support for Ruby 2.7 (EOL)
+- **React on Rails 15+**: Required for RSC and streaming features
+- **Node 20+**: Strongly recommended (older versions require specific package.json resolutions)
+
+### Package.json Resolutions (for Node < 20)
+
+If using older Node versions, add to your `package.json`:
+
+```json
+"resolutions": {
+  "@fastify/formbody": "^7.4.0",
+  "@fastify/multipart": "^8.3.1",
+  "fastify": "^4.29.0"
+}
+```
+
+## Getting Started
+
+- **RSC Tutorial**: [Complete React Server Components Guide](../react-server-components/tutorial.md)
+- **Streaming SSR**: [Streaming Server Rendering Documentation](../streaming-server-rendering.md)
+- **Error Reporting**: [Error Reporting and Tracing Setup](../node-renderer/error-reporting-and-tracing.md)
+- **Performance**: [Caching and Optimization Guide](../caching.md)
+
+## Support & Community
+
+- **Documentation**: Comprehensive guides and tutorials available
+- **Examples**: Working examples in the spec/dummy application
+- **GitHub**: Active development and community support
+- **Discussions**: Join the [React on Rails community](https://forum.shakacode.com/) for help and updates
+
+---
+
+_React on Rails Pro 4.0 represents a major evolution in server-side React rendering, bringing React Server Components and advanced streaming to the Rails ecosystem with enterprise-grade performance and reliability._

data/docs/release-notes/v4-react-server-components.md

@@ -10,33 +10,33 @@ We're thrilled to announce a major update: React on Rails Pro now supports **Rea
 
 ## 🎯 What This Means for Your Applications
 
-* **Faster load times**
-* **Smaller JavaScript bundles**
-* **Better Core Web Vitals**
-* **Improved SEO**
-* **Smoother user interactions**
+- **Faster load times**
+- **Smaller JavaScript bundles**
+- **Better Core Web Vitals**
+- **Improved SEO**
+- **Smoother user interactions**
 
 ## 🔥 React Server Components
 
 Server Components execute on the server and stream HTML to the client—no extra JavaScript in your bundle. Real‑world results include:
 
-* **62% reduction** in client‑side bundle size on productonboarding.com when migrating to RSC [[1]]
-* **63% improvement** in Google Speed Index on the RSC version of the same site [[1]]
-* **52% smaller** JavaScript codebase and Lighthouse scores rising from \~50 to 90+ on GeekyAnts.com [[2]]
+- **62% reduction** in client‑side bundle size on productonboarding.com when migrating to RSC [[1]]
+- **63% improvement** in Google Speed Index on the RSC version of the same site [[1]]
+- **52% smaller** JavaScript codebase and Lighthouse scores rising from \~50 to 90+ on GeekyAnts.com [[2]]
 
 ## 🌊 SSR Streaming
 
 SSR Streaming sends HTML to the browser in chunks as it’s generated, enabling progressive rendering:
 
-* **30% faster** full‑page load times at Hulu by combining streaming SSR with Server Components [[3]]
-* Popular libraries like styled‑components v3.1.0 have introduced streaming SSR support as the next generation of React app rendering [[4]]
+- **30% faster** full‑page load times at Hulu by combining streaming SSR with Server Components [[3]]
+- Popular libraries like styled‑components v3.1.0 have introduced streaming SSR support as the next generation of React app rendering [[4]]
 
 ## 📊 Core Web Vitals & TTI Improvements
 
-* **60% faster** Time to Interactive on Meta’s developer portal after adopting RSC (from 3.5 s to \~1.4 s) [[5]]
-* **45% quicker** First Contentful Paint in the same migration [[5]]
-* **50% lower** server response time with Server Components [[5]]
-* **15% improvement** in Core Web Vitals and **23% reduction** in Time to First Byte at Airbnb after RSC migration [[5]]
+- **60% faster** Time to Interactive on Meta’s developer portal after adopting RSC (from 3.5 s to \~1.4 s) [[5]]
+- **45% quicker** First Contentful Paint in the same migration [[5]]
+- **50% lower** server response time with Server Components [[5]]
+- **15% improvement** in Core Web Vitals and **23% reduction** in Time to First Byte at Airbnb after RSC migration [[5]]
 
 ---
 
@@ -45,7 +45,7 @@ Adopting these features in React on Rails Pro will help you deliver faster, lean
 **Ready to get started?**
 
 1. Update to the latest React on Rails Pro version
-2. Follow our [RSC & SSR Streaming migration guide](https://github.com/shakacode/react_on_rails_pro/blob/abanoubghadban/pro465/use-rsc-payload-to-render-server-components-on-server/docs/react-server-components-tutorial.md)
+2. Follow our [RSC & SSR Streaming migration guide](../react-server-components/tutorial.md)
 
 Let’s make your apps faster—together.
 
@@ -63,4 +63,4 @@ Let’s make your apps faster—together.
 [2]: https://geekyants.com/en-gb/blog/boosting-performance-with-nextjs-and-react-server-components-a-geekyantscom-case-study
 [3]: https://www.compilenrun.com/docs/framework/nextjs/nextjs-ecosystem/nextjs-case-studies/#case-study-3-hulus-streaming-platform
 [4]: https://medium.com/styled-components/v3-1-0-such-perf-wow-many-streams-c45c434dbd03
-[5]: https://questlab.pro/blog-posts/web-development/wd-pl-2024-articleId912i1h212818
+[5]: https://web.archive.org/web/20250908030148/https://questlab.pro/blog-posts/web-development/wd-pl-2024-articleId912i1h212818

data/docs/streaming-server-rendering.md

@@ -112,7 +112,6 @@ end
 
 You can test your application by running `rails server` and navigating to the appropriate route.
 
-
 6. **What Happens During Streaming**
 
 When a user visits the page, they'll experience the following sequence:
@@ -152,9 +151,7 @@ For example, with our `MyStreamingComponent`, the sequence might be:
 
 <script>
   // This implementation is slightly simplified
-  document.getElementById('s0').replaceChildren(
-    document.getElementById('b0')
-  );
+  document.getElementById('s0').replaceChildren(document.getElementById('b0'));
 </script>
 ```
 
@@ -182,6 +179,7 @@ Streaming SSR is particularly valuable in specific scenarios. Here's when to con
 ### Best Practices for Streaming
 
 1. **Component Structure**
+
    ```jsx
    // Good: Independent sections that can stream separately
    <Layout>

data/docs/troubleshooting.md

@@ -1,6 +1,7 @@
 # Troubleshooting
 
 ## Invalid Token Workaround
+
 On June 27, 2024, tokens mysteriously did not work for a few hours. The problem resolved itself within a few hours.
 
 If you do see this problem, get in touch with the package maintainers via Slack. You can also message
@@ -10,6 +11,7 @@ As an alternative to the token issue, if you have an account with access to the
 create a new token and follow these steps.
 
 To create a new token, visit https://github.com/settings/apps:
+
 1. Developer Settings
 2. Personal access tokens
 3. Tokens (classic)
@@ -18,7 +20,8 @@ To create a new token, visit https://github.com/settings/apps:
 6. Repo privileges (not ideal) but shouldn't last long
 
 Then follow these steps to use your token:
-* [Ruby Gem](https://github.com/shakacode/react_on_rails_pro/blob/master/docs/installation.md#using-a-branch-in-your-gemfile)
-* [Node Package](https://github.com/shakacode/react_on_rails_pro/blob/master/docs/installation.md#instructions-for-using-a-branch)
+
+- [Ruby Gem](https://github.com/shakacode/react_on_rails_pro/blob/master/docs/installation.md#using-a-branch-in-your-gemfile)
+- [Node Package](https://github.com/shakacode/react_on_rails_pro/blob/master/docs/installation.md#instructions-for-using-a-branch)
 
 Note that this token gives `repo` access, so you want to revoke this token ASAP.

data/docs/updating.md

@@ -23,8 +23,12 @@ React on Rails Pro packages are now **publicly distributed** via npmjs.org and R
 
 Package names have changed:
 
-- **Scoped** (old): `@shakacode-tools/react-on-rails-pro-node-renderer`
-- **Unscoped** (new): `react-on-rails-pro-node-renderer`
+| Package       | Old (Scoped)                                        | New (Unscoped)                     |
+| ------------- | --------------------------------------------------- | ---------------------------------- |
+| Client        | `react-on-rails`                                    | `react-on-rails-pro`               |
+| Node Renderer | `@shakacode-tools/react-on-rails-pro-node-renderer` | `react-on-rails-pro-node-renderer` |
+
+**Important:** Pro users should now import from `react-on-rails-pro` instead of `react-on-rails`. The Pro package includes all core features plus Pro-exclusive functionality.
 
 ### Your Current Setup (GitHub Packages)
 
@@ -98,11 +102,12 @@ rm .npmrc
 
 #### Step 3: Update package.json
 
-Change the package name from **scoped** to **unscoped**:
+**Add the client package** and update the node renderer package name:
 
 ```diff
 {
   "dependencies": {
++   "react-on-rails-pro": "^16.2.0",
 -   "@shakacode-tools/react-on-rails-pro-node-renderer": "16.1.1"
 +   "react-on-rails-pro-node-renderer": "^16.2.0"
   }
@@ -117,18 +122,36 @@ npm install
 yarn install
 ```
 
-#### Step 4: Update Require Statements
+#### Step 4: Update Import Statements
+
+**Client code:** Change all imports from `react-on-rails` to `react-on-rails-pro`:
+
+```diff
+- import ReactOnRails from 'react-on-rails';
++ import ReactOnRails from 'react-on-rails-pro';
+```
+
+**Pro-exclusive features** (React Server Components, async loading):
+
+```diff
+- import { RSCRoute } from 'react-on-rails/RSCRoute';
++ import { RSCRoute } from 'react-on-rails-pro/RSCRoute';
 
-Update all require/import statements to use the **unscoped** package name:
+- import registerServerComponent from 'react-on-rails/registerServerComponent/client';
++ import registerServerComponent from 'react-on-rails-pro/registerServerComponent/client';
+
+- import { wrapServerComponentRenderer } from 'react-on-rails/wrapServerComponentRenderer/client';
++ import { wrapServerComponentRenderer } from 'react-on-rails-pro/wrapServerComponentRenderer/client';
+```
 
-**In your node renderer configuration file:**
+**Node renderer configuration file:**
 
 ```diff
 - const { reactOnRailsProNodeRenderer } = require('@shakacode-tools/react-on-rails-pro-node-renderer');
 + const { reactOnRailsProNodeRenderer } = require('react-on-rails-pro-node-renderer');
 ```
 
-**If using integrations (Sentry, Honeybadger):**
+**Node renderer integrations (Sentry, Honeybadger):**
 
 ```diff
 - require('@shakacode-tools/react-on-rails-pro-node-renderer/integrations/sentry').init();
@@ -171,10 +194,12 @@ bundle list | grep react_on_rails_pro
 #### 2. Verify NPM Package Installation
 
 ```bash
-npm list react-on-rails-pro-node-renderer
-# or
-yarn list --pattern react-on-rails-pro-node-renderer
+# Verify client package
+npm list react-on-rails-pro
+# Should show: react-on-rails-pro@16.2.0 or higher
 
+# Verify node renderer (if using)
+npm list react-on-rails-pro-node-renderer
 # Should show: react-on-rails-pro-node-renderer@16.2.0 or higher
 ```
 
@@ -202,11 +227,22 @@ If the license is invalid or missing, you'll see an error with instructions.
 - Run `bundle install` again
 - Check that you have the correct version specified
 
-#### "Cannot find module 'react-on-rails-pro-node-renderer'"
+#### "Cannot find module 'react-on-rails-pro'" or "Cannot find module 'react-on-rails-pro-node-renderer'"
 
-- Verify you updated all require statements to the unscoped name
+- Verify you added `react-on-rails-pro` to your package.json dependencies
+- Verify you updated all import/require statements to use the correct package names
 - Delete `node_modules` and reinstall: `rm -rf node_modules && npm install`
-- Check that package.json has the correct unscoped package name
+
+#### "Cannot mix react-on-rails (core) with react-on-rails-pro"
+
+This error occurs when you import from both `react-on-rails` and `react-on-rails-pro`. Pro users should **only** import from `react-on-rails-pro`:
+
+```diff
+- import ReactOnRails from 'react-on-rails';
++ import ReactOnRails from 'react-on-rails-pro';
+```
+
+The Pro package re-exports everything from core, so you don't need both.
 
 #### "License validation failed"
 

data/lib/react_on_rails_pro/request.rb

@@ -7,9 +7,17 @@ require_relative "stream_request"
 module ReactOnRailsPro
   class Request # rubocop:disable Metrics/ClassLength
     class << self
+      # Mutex for thread-safe connection management.
+      # Using a constant eliminates the race condition that would exist with @mutex ||= Mutex.new
+      CONNECTION_MUTEX = Mutex.new
+
       def reset_connection
-        @connection&.close
-        @connection = create_connection
+        CONNECTION_MUTEX.synchronize do
+          new_conn = create_connection
+          old_conn = @connection
+          @connection = new_conn
+          old_conn&.close
+        end
       end
 
       def render_code(path, js_code, send_bundle)
@@ -83,7 +91,14 @@ module ReactOnRailsPro
       private
 
       def connection
-        @connection ||= create_connection
+        # Fast path: return existing connection without locking (lock-free for 99.99% of calls)
+        conn = @connection
+        return conn if conn
+
+        # Slow path: initialize with lock (only happens once per process)
+        CONNECTION_MUTEX.synchronize do
+          @connection ||= create_connection
+        end
       end
 
       def perform_request(path, **post_options) # rubocop:disable Metrics/AbcSize,Metrics/CyclomaticComplexity

data/lib/react_on_rails_pro/version.rb

@@ -1,6 +1,6 @@
 # frozen_string_literal: true
 
 module ReactOnRailsPro
-  VERSION = "16.2.0.beta.20"
+  VERSION = "16.2.0.rc.0"
   PROTOCOL_VERSION = "2.0.0"
 end

data/rakelib/dummy_apps.rake

@@ -7,12 +7,12 @@ include ReactOnRailsPro::TaskHelpers
 # rubocop:enable Style/MixinUsage
 
 namespace :dummy_app do
-  task :yarn_install do
-    yarn_install_cmd = "yarn install --frozen-lockfile --mutex network"
-    sh_in_dir(dummy_app_dir, yarn_install_cmd)
+  task :pnpm_install do
+    pnpm_install_cmd = "pnpm install --frozen-lockfile"
+    sh_in_dir(dummy_app_dir, pnpm_install_cmd)
   end
 
-  task dummy_app: [:yarn_install] do
+  task dummy_app: [:pnpm_install] do
     dummy_app_dir = File.join(gem_root, "spec/dummy")
     bundle_install_in(dummy_app_dir)
   end

data/rakelib/lint.rake

@@ -19,7 +19,7 @@ namespace :lint do
 
   desc "Run eslint as shell"
   task :eslint do
-    sh_in_dir(gem_root, "yarn run eslint")
+    sh_in_dir(gem_root, "pnpm run eslint")
   end
 
   desc "Run all eslint, rubocop linters. Skip ruby-lint and scss"

data/rakelib/run_rspec.rake

@@ -36,9 +36,9 @@ namespace :run_rspec do
   end
 end
 
-desc "js tests (same as 'yarn run test')"
+desc "js tests (same as 'pnpm run test')"
 task :js_tests do
-  sh "yarn run test"
+  sh "pnpm run test"
 end
 
 msg = <<~DESC
@@ -77,5 +77,5 @@ end
 
 def clean_gen_assets(dir)
   path = calc_path(dir)
-  sh_in_dir(path.realpath, "yarn run build:clean")
+  sh_in_dir(path.realpath, "pnpm run build:clean")
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: react_on_rails_pro
 version: !ruby/object:Gem::Version
-  version: 16.2.0.beta.20
+  version: 16.2.0.rc.0
 platform: ruby
 authors:
 - Justin Gordon
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2025-12-13 00:00:00.000000000 Z
+date: 2025-12-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: addressable
@@ -128,14 +128,14 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 16.2.0.beta.20
+        version: 16.2.0.rc.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 16.2.0.beta.20
+        version: 16.2.0.rc.0
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement