react_on_rails_pro 16.2.0.test.6 → 16.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 732ae79d182e8e0686150a28e46d145e6cd06fea16a03601f9c7827295959d86
-  data.tar.gz: f0afe72172530e35186717d35ab99b3b5cf7eea0cb8d1c98c4ae11b845bb73bf
+  metadata.gz: aa36f2c2ebdd0fd2c8b42a44ea5809bf6b406ad5dfefe82f3f87643fd361368c
+  data.tar.gz: 6d0c478dea603606fe530d2e6dcec612240263dc9bc32e001d166c38f86932be
 SHA512:
-  metadata.gz: 2a5f90e25b4251c4de23d34d84ecd6e6fcb380a3ee54f1484db1e3814cf416035ca270f70ce469199aebdf07057a3629c22e5198d3a4a15057ce9a12d0c86b85
-  data.tar.gz: 549566b49134e302875deb6419d140f30c780f50831adb419870b5404eeba2db8b798710a61fbccf1cbfd9efe295905829f4f7b9a87af00fd750a48fed433a03
+  metadata.gz: 33992470f693ecdb68975cbc2bec28c2ae04f059c9e4af5e9b6debdad0a9d64894df6642baf80bd765be4d46f8e526084ab516541c26ba6c5b0bb6281d570d49
+  data.tar.gz: '08c66853fd310d4d961e2c8045a701404c67fb6f361c6d3a7c00b887c3c619c88bf3b563604aacf79bd1850f596d25a9c74403c0a7337dc788df60ef19c0aa3f'

data/.prettierignore

@@ -9,3 +9,6 @@ spec/dummy/.yalc/
 
 # File Generated by ROR FS-based Registry
 **/generated
+
+# Prettier doesn't understand ERB in RuboCop config
+.rubocop.yml

data/.rubocop.yml

@@ -1,111 +1,31 @@
-# This is the configuration used to check the rubocop source code.
-# Check out: https://github.com/bbatsov/rubocop
-require:
-  - rubocop-performance
-  - rubocop-rspec
+# Inherits from root config
+inherit_from: ../.rubocop.yml
 
-AllCops:
-  NewCops: enable
-  DisplayCopNames: true
-  TargetRubyVersion: 3.0
-
-  Include:
-    - '**/Rakefile'
-    - '**/config.ru'
-    - 'Gemfile'
-    - '**/*.rb'
-    - '**/*.rake'
+# Merge Exclude arrays with parent instead of replacing them
+inherit_mode:
+  merge:
+    - Exclude
 
+AllCops:
   Exclude:
   <% `git status --ignored --porcelain`.lines.grep(/^!! /).each do |path| %>
     - <%= path.sub(/^!! /, '') %>
   <% end %>
-    - '**/node_modules/**/*'
     - 'db/schema.rb'
     - 'db/seeds.rb'
-    - 'spec/fixtures/**/*'
     - 'spec/dummy/db/schema.rb'
     - 'spec/dummy/bin/**/*'
-    - 'node_modules/**/*'
-    - 'coverage/**/*'
     - 'bin/**/*'
-    - 'vendor/**/*'
-
-Naming/FileName:
-  Exclude:
-    - '**/Gemfile'
-    - '**/Rakefile'
-
-Layout/LineLength:
-  Max: 120
-
-Style/StringLiterals:
-  EnforcedStyle: double_quotes
-
-Style/Documentation:
-  Enabled: false
-
-Style/HashEachMethods:
-  Enabled: true
-
-Style/HashTransformKeys:
-  Enabled: true
-
-Style/HashTransformValues:
-  Enabled: true
-
-Metrics/AbcSize:
-  Max: 28
-
-Metrics/CyclomaticComplexity:
-  Max: 8
-
-Metrics/PerceivedComplexity:
-  Max: 10
-
-Metrics/ClassLength:
-  Max: 140
-
-Metrics/ParameterLists:
-  Max: 5
-  CountKeywordArgs: false
-
-Metrics/MethodLength:
-  Max: 41
-
-Metrics/ModuleLength:
-  Max: 180
-
-RSpec/DescribeClass:
-  Enabled: false
-
-RSpec/ExampleLength:
-  Enabled: false
-
-RSpec/MessageSpies:
-  Enabled: false
-
-RSpec/NestedGroups:
-  Max: 5
 
 RSpec/BeforeAfterAll:
   Exclude:
     - 'spec/react_on_rails/generators/dev_tests_generator_spec.rb'
     - 'spec/react_on_rails/generators/install_generator_spec.rb'
 
-RSpec/MessageChain:
-  Enabled: false
-
-RSpec/MultipleExpectations:
-  Enabled: false
-
 RSpec/MultipleDescribes:
   Exclude:
     - 'spec/dummy/spec/system/integration_spec.rb'
 
-RSpec/MultipleMemoizedHelpers:
-  Max: 12
-
 RSpec:
   Language:
     Expectations:
@@ -115,6 +35,3 @@ RSpec:
 Style/GlobalVars:
   Exclude:
     - 'spec/dummy/config/environments/development.rb'
-
-Style/FrozenStringLiteralComment:
-  EnforcedStyle: always

data/CHANGELOG.md

@@ -17,7 +17,11 @@ You can find the **package** version numbers from this repo's tags and below in
 
 ## [Unreleased]
 
-_Add changes in master not yet tagged._
+Changes since the last non-beta release.
+
+### [v16.2.0.rc.0] - 2025-12-29
+
+Changes since the last non-beta release.
 
 ### Improved
 
@@ -30,7 +34,6 @@ _Add changes in master not yet tagged._
 - Added `cached_stream_react_component` helper method, similar to `cached_react_component` but for streamed components.
 - **License Validation System**: Implemented comprehensive JWT-based license validation with offline verification using RSA-256 signatures. License validation occurs at startup in both Ruby and Node.js environments. Supports required fields (`sub`, `iat`, `exp`) and optional fields (`plan`, `organization`, `iss`). FREE evaluation licenses are available for 3 months at [shakacode.com/react-on-rails-pro](https://shakacode.com/react-on-rails-pro). [PR #1857](https://github.com/shakacode/react_on_rails/pull/1857) by [AbanoubGhadban](https://github.com/AbanoubGhadban).
 - **Pro-Specific Configurations Moved from Open-Source**: The following React Server Components (RSC) configurations are now exclusively in the Pro gem and should be configured in `ReactOnRailsPro.configure`:
-
   - `rsc_bundle_js_file` - Path to the RSC bundle file
   - `react_server_client_manifest_file` - Path to the React server client manifest
   - `react_client_manifest_file` - Path to the React client manifest
@@ -38,7 +41,6 @@ _Add changes in master not yet tagged._
   These configurations were previously available in the open-source `ReactOnRails.configure` block but have been moved to Pro where they belong since RSC is a Pro-only feature.
 
 - **Streaming View Helpers Now Pro-Exclusive**: The following view helpers are now defined exclusively in the Pro gem:
-
   - `stream_react_component` - Progressive SSR using React 18+ streaming
   - `rsc_payload_react_component` - RSC payload rendering
 
@@ -48,8 +50,16 @@ _Add changes in master not yet tagged._
 
 ### Fixed
 
+- **Thread-Safe Connection Management**: Fixed race conditions in `ReactOnRailsPro::Request` connection management. The lazy initialization (`@connection ||= create_connection`) was not atomic, allowing multiple threads to create duplicate connections at startup. Now uses a mutex with double-checked locking pattern for thread-safe initialization while maintaining lock-free reads for optimal performance. [PR 2259](https://github.com/shakacode/react_on_rails/pull/2259) by [AbanoubGhadban](https://github.com/AbanoubGhadban).
+
+- **Legacy Module Resolver Compatibility**: Added `main` field to `react-on-rails-pro` and `react-on-rails-pro-node-renderer` package.json files for compatibility with legacy module resolvers like `eslint-import-resolver-node` that don't support Node.js conditional exports. [PR 2256](https://github.com/shakacode/react_on_rails/pull/2256) by [ihabadham](https://github.com/ihabadham).
+
+- **SECURITY: CVE-2025-55182 - React Server Components RCE Vulnerability**: by updating `react-on-rails-rsc` peer dependency to `v19.0.3` which mitigates that vulnerability. Also, users should update `react` and `react-dom` package versions to `v19.0.1` to ensure complete mitigation. [PR 2175](https://github.com/shakacode/react_on_rails/pull/2175) by [AbanoubGhadban](https://github.com/AbanoubGhadban).
+
 - Fixed compatibility issue with httpx 1.6.x by explicitly requiring http-2 >= 1.1.1. [PR 2141](https://github.com/shakacode/react_on_rails/pull/2141) by [AbanoubGhadban](https://github.com/AbanoubGhadban).
 
+- **Client Disconnect Handling for Streaming**: Added error handling for client disconnects during streaming. When a client disconnects mid-stream (browser closed, network drop), the system now catches `IOError`/`Errno::EPIPE`, sets a `client_disconnected` flag, stops the barrier to cancel producer tasks, and logs the disconnect for debugging. Prevents wasted CPU from producers continuing after the writer fails. [PR 2137](https://github.com/shakacode/react_on_rails/pull/2137) by [justin808](https://github.com/justin808).
+
 - **Node Renderer Worker Restart**: Fixed "descriptor closed" error that occurred when the node renderer restarts while handling an in-progress request (especially streaming requests). Workers now perform graceful shutdowns: they disconnect from the cluster to stop receiving new requests, wait for active requests to complete, then shut down cleanly. A configurable `gracefulWorkerRestartTimeout` ensures workers are forcibly killed if they don't shut down in time. [PR 1970](https://github.com/shakacode/react_on_rails/pull/1970) by [AbanoubGhadban](https://github.com/AbanoubGhadban).
 
 - **Body Duplication Bug On Streaming**: Fixed a bug that happens while streaming if the node renderer connection closed after streaming some chunks to the client. [PR 1995](https://github.com/shakacode/react_on_rails/pull/1995) by [AbanoubGhadban](https://github.com/AbanoubGhadban).
@@ -96,7 +106,7 @@ _Add changes in master not yet tagged._
   - Seamlessly use React Server Components in your Rails apps
   - Reduce client bundle sizes
   - Enable powerful new patterns for data fetching
-  - [See the full tutorial](https://www.shakacode.com/react-on-rails-pro/docs/react-server-components-tutorial)
+  - [See the full tutorial](https://www.shakacode.com/react-on-rails-pro/docs/react-server-components/tutorial)
 
 [PR 422](https://github.com/shakacode/react_on_rails_pro/pull/422) by [AbanoubGhadban](https://github.com/AbanoubGhadban).
 
@@ -109,7 +119,6 @@ _Add changes in master not yet tagged._
 ### Changed
 
 - [PR 511](https://github.com/shakacode/react_on_rails_pro/pull/511) by [Romex91](https://github.com/Romex91)
-
   - Set `bodyLimit` to 100 MB by default to fix error 413.
   - Add `fastifyServerOptions` to the config
 
@@ -256,7 +265,6 @@ React 18 is now supported! Check the [React on Rails CHANGELOG.md](https://githu
 ### Added
 
 - [PR 220](https://github.com/shakacode/react_on_rails_pro/pull/220) by [justin808](https://github.com/justin808).
-
   - **Add `ssr_timeout` configuration** so the Rails server will not wait more than this many seconds for a SSR request to return once issued.
   - Change default for `renderer_use_fallback_exec_js` to `false`.
   - Change default log level to info.
@@ -536,7 +544,8 @@ Above changes in [PR 52](https://github.com/shakacode/react_on_rails_pro/pull/52
 - advanced error handling
 
 [HEAD compared to 3.2.1]: https://github.com/shakacode/react_on_rails_pro/compare/3.3.1...HEAD
-[Unreleased]: https://github.com/shakacode/react_on_rails_pro/compare/4.0.0-rc-15...HEAD
+[Unreleased]: https://github.com/shakacode/react_on_rails/compare/v16.2.0.rc.0...master
+[v16.2.0.rc.0]: https://github.com/shakacode/react_on_rails/compare/16.1.1...v16.2.0.rc.0
 [4.0.0-rc.15]: https://github.com/shakacode/react_on_rails_pro/compare/4.0.0-rc.14...4.0.0-rc.15
 [4.0.0.rc.11]: https://github.com/shakacode/react_on_rails_pro/compare/4.0.0-rc.9...4.0.0-rc.11
 [4.0.0.rc.9]: https://github.com/shakacode/react_on_rails_pro/compare/4.0.0-rc.6...4.0.0-rc.9

data/CONTRIBUTING.md

@@ -4,34 +4,36 @@
 
 Install [yalc](https://github.com/wclr/yalc).
 
-
 ```sh
+pnpm install -r
 cd react_on_rails_pro
-bundle && yarn && cd spec/dummy && bundle && yarn
+bundle && cd spec/dummy && bundle && pnpm install
 ```
+
 To use the `React 18 Apollo with GraphQL` example you need to seed the testing database inside `spec/dummy` directory.
+
 ```sh
 rake db:seed
 ```
 
-
 See the example apps under `/spec`
 
 ## Summary
 
 For non-doc fixes:
 
-* Provide changelog entry in the [unreleased section of the CHANGELOG.md](https://github.com/shakacode/react_on_rails_pro/blob/master/CHANGELOG.md#unreleased).
-* Ensure CI passes and that you added a test that passes with the fix and fails without the fix.
-* Squash all commits down to one with a nice commit message *ONLY* once final review is given. Make sure this single commit is rebased on top of master.
-* Please address all code review comments.
-* Ensure that docs are updated accordingly if a feature is added.
+- Provide changelog entry in the [unreleased section of the CHANGELOG.md](https://github.com/shakacode/react_on_rails_pro/blob/master/CHANGELOG.md#unreleased).
+- Ensure CI passes and that you added a test that passes with the fix and fails without the fix.
+- Squash all commits down to one with a nice commit message _ONLY_ once final review is given. Make sure this single commit is rebased on top of master.
+- Please address all code review comments.
+- Ensure that docs are updated accordingly if a feature is added.
 
 ## Commit Messages
 
 From [How to Write a Git Commit Message](http://chris.beams.io/posts/git-commit/)
 
-#### The seven rules of a great git commit message
+### The seven rules of a great git commit message
+
 > Keep in mind: This has all been said before.
 
 1. Separate subject from body with a blank line
@@ -42,21 +44,21 @@ From [How to Write a Git Commit Message](http://chris.beams.io/posts/git-commit/
 1. Wrap the body at 72 characters
 1. Use the body to explain what and why vs. how
 
-
 ## Doc Changes
 
-When making doc changes, we want the change to work on both https://www.shakacode.com/react-on-rails-pro/docs/ and when browsing the GitHub repo. 
+When making doc changes, we want the change to work on both [the ShakaCode docs site](https://www.shakacode.com/react-on-rails-pro/docs/) and when browsing the GitHub repo.
 The issue is that the Shakacode site is generated only from files in [`docs`](./docs), so any references from them to non-doc files must use the full GitHub URL.
 
 ### Links to other docs:
-* When making references to doc files, use a relative URL path like:
-`[Installation Overview](docs/basics/installation-overview.md)`
 
-* When making references to source code files, use a full url path like:
-`[spec/dummy/config/initializers/react_on_rails.rb](https://github.com/shakacode/react_on_rails_pro/tree/master/spec/dummy/config/initializers/react_on_rails.rb)`
+- When making references to doc files, use a relative URL path like:
+  `[Installation Overview](docs/basics/installation-overview.md)`
 
+- When making references to source code files, use a full url path like:
+  `[spec/dummy/config/initializers/react_on_rails.rb](https://github.com/shakacode/react_on_rails_pro/tree/master/spec/dummy/config/initializers/react_on_rails.rb)`
 
 ## To run tests:
+
 See [Run NPM JS tests](#run-npm-js-tests) for the JS tests and [RSpec Testing](#rspec-testing) for the Ruby tests.
 
 See [Dev Initial Setup](#dev-initial-setup) below for, well... initial setup.
@@ -107,30 +109,33 @@ script/ci-changes-detector origin/master
 ### CI Best Practices for Pro
 
 ✅ **DO:**
+
 - Run `bin/ci-local` from repository root before pushing
 - Test Pro changes alongside main gem changes if modifying both
 - Use `bin/ci-local --fast` during rapid iteration
 
 ❌ **DON'T:**
+
 - Push Pro changes without testing locally first
 - Modify both Pro and main gem without running full tests
 
 For comprehensive CI documentation, see [`../docs/CI_OPTIMIZATION.md`](../docs/CI_OPTIMIZATION.md) in the repository root.
 
 # IDE/Editor Setup
-It's critical to configure your IDE/editor to ignore certain directories. Otherwise your IDE might slow to a crawl!
 
-* /coverage
-* /tmp
-* /node_modules
-* /spec/dummy/app/assets/webpack
-* /spec/dummy/log
-* /spec/dummy/node_modules
-* /spec/dummy/client/node_modules
-* /spec/dummy/tmp
+It's critical to configure your IDE/editor to ignore certain directories. Otherwise your IDE might slow to a crawl!
 
+- /coverage
+- /tmp
+- /node_modules
+- /spec/dummy/app/assets/webpack
+- /spec/dummy/log
+- /spec/dummy/node_modules
+- /spec/dummy/client/node_modules
+- /spec/dummy/tmp
 
 # Configuring your test app to use your local fork
+
 You can test the `react_on_rails_pro` gem using your own external test_app or the gem's internal `spec/dummy` app. The `spec/dummy` app is an example of the various setup techniques you can use with the gem.
 As of 2018-04-28, this directory mirrors the test app spec/dummy on https://github.com/shakacode/react_on_rails plus a few additional tests.
 
@@ -143,15 +148,17 @@ As of 2018-04-28, this directory mirrors the test app spec/dummy on https://gith
 ```
 
 ## Testing the Ruby Gem
+
 If you want to test the ruby parts of the gem with an application before you release a new version of the gem, you can specify the path to your local version via your test app's Gemfile:
 
 ```ruby
 gem "react_on_rails_pro", path: "../path-to-react_on_rails_pro"
 gem "react_on_rails"
 ```
+
 ================================================================================
 
-Set `config.server_renderer = "NodeRenderer"` in your  `ReactOnRailsPro.configure` block in the initializer.
+Set `config.server_renderer = "NodeRenderer"` in your `ReactOnRailsPro.configure` block in the initializer.
 
 After making this change, run `bundle install`.
 
@@ -159,6 +166,7 @@ After making this change, run `bundle install`.
 > You will need to restart your Rails application if you make any changes to the gem.
 
 ## Testing the Node package for react_on_rails_pro
+
 In addition to testing the Ruby parts out, you can also test the node package parts of the gem with an external application.
 
 To do this, follow the instructions in the
@@ -166,19 +174,21 @@ To do this, follow the instructions in the
 
 ### Example: Testing NPM changes with the dummy app
 
-1. Add `console.log('Hello!')` [here](https://github.com/shakacode/react_on_rails_pro/blob/more_test_and_docs/packages/node-renderer/src/ReactOnRailsProNodeRenderer.js#L6) in `packages/node-renderer/src/ReactOnRailsProNodeRenderer.js` to confirm we're getting an update to the node package.
-2. The `preinstall` script of `spec/dummy` builds the NPM package and sets up `yalc` to use it for the renderer. 
-   It's run automatically when you run `yarn install`. 
+1. Add `console.log('Hello!')` [here](https://github.com/shakacode/react_on_rails_pro/blob/master/packages/node-renderer/src/ReactOnRailsProNodeRenderer.ts#L6) in `packages/node-renderer/src/ReactOnRailsProNodeRenderer.ts` to confirm we're getting an update to the node package.
+2. The `preinstall` script of `spec/dummy` builds the NPM package and sets up `yalc` to use it for the renderer.
+   It's run automatically when you run `pnpm install`.
 3. Refresh the browser if the server is already running or start the server using `foreman start -f Procfile.dev` from `spec/dummy` and navigate to `http://localhost:3000/`. You will now see the `Hello!` message printed in the browser's console.
 
+<!-- prettier-ignore -->
 > [!NOTE]
 > `yalc` makes the NPM package available globally on the machine.
 > So, if you have the repo checked out more than once to compare behavior between branches,
-> make sure to run `yarn install` every time you switch to a new copy.
+> make sure to run `pnpm install` every time you switch to a new copy.
 
 # Development Setup for Gem and Node Package Contributors
 
 ## Checklist before Committing
+
 1. Run all JS tests, dummy app tests and linters.
 2. Did you need any more tests for your change?
 3. Did you document your change? Update the README.md?
@@ -186,12 +196,13 @@ To do this, follow the instructions in the
 ## Dev Initial Setup
 
 ### Prereqs
-After checking out the repo, making sure you have rvm and nvm setup (setup ruby and node), cd to `spec/dummy` and run `bin/setup` to install ruby dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
 
+After checking out the repo, making sure you have rvm and nvm setup (setup ruby and node), cd to `spec/dummy` and run `bin/setup` to install ruby dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
 
 ### Building the Node Package for Development
 
 At the root:
+
 ```
 nps build
 ```
@@ -207,6 +218,7 @@ This is a possible update to package.json to debug the lockfile. Notice the `NOD
 See https://nodejs.org/api/util.html#util_util_debuglog_section for details on `debuglog`.
 
 ### Local Node Package
+
 Because the example and dummy apps rely on the `react_on_rails_pro` node package, they should link directly to your local version to pick up any changes you may have made to that package.
 To achieve this, you can use `yalc`.
 The easy way to do this is to run the command below in the dummy app root directory.
@@ -215,11 +227,11 @@ For more information check the script section of the
 
 ```sh
 cd spec/dummy
-yarn install
+pnpm install -r
 ```
 
 > [!NOTE]
-> This runs npm under the hood as explained in the **Test NPM for react_on_rails_pro** section above.
+> This uses yalc under the hood as explained in the **Example: Testing NPM changes with the dummy app** section above.
 
 From now on, the example and dummy apps will use your local packages/node-renderer folder as the `react_on_rails_pro` node package.
 
@@ -227,51 +239,55 @@ From now on, the example and dummy apps will use your local packages/node-render
 
 ```sh
 cd react_on_rails_pro
-yarn install
+pnpm install -r
 ```
 
-Or run this, which builds the yarn package, then the webpack files for spec/dummy, and finally runs tests in
+Or run this, which builds the pnpm package, then the webpack files for spec/dummy, and finally runs tests in
 spec/dummy.
 
-
 ```sh
 # Optionally change default selenium_firefox driver
 # export DRIVER=poltergeist
 cd react_on_rails_pro
-yarn run dummy:spec
+pnpm run dummy:spec
 ```
 
 ### Run NPM JS tests
 
 ```sh
 cd react_on_rails_pro
-yarn test
+pnpm test
 ```
 
 ### Debugging NPM JS tests
 
 Example of using ndb to debug a test
+
 ```bash
-ndb $(yarn bin)/jest --runInBand  packages/node-renderer/tests/**/*.test.[jt]s -t 'FriendsAndGuests bundle for commit 1a7fe417'
+ndb $(pnpm bin)/jest --runInBand  packages/node-renderer/tests/**/*.test.[jt]s -t 'FriendsAndGuests bundle for commit 1a7fe417'
 ```
+
 Hit F8 and then a debugger statement within the test will get hit.
 
 ### Creating new VM tests
+
 1. copy a server bundle to `packages/node-renderer/tests/fixtures/projects/<project-name>/<commit>`
 2. create a directory with a hash representing the commit of the project
 
 ### Async issues with Jest
+
 Beware that Jest runs multiple test files synchronously, so you can't use the same temporary directory
-between tests. See the file [`packages/node-renderer/tests/helper.ts`](packages/node-renderer/tests/helper.ts) for how we handle this.
+between tests. See the file [`packages/node-renderer/tests/helper.ts`](https://github.com/shakacode/react_on_rails_pro/blob/master/packages/node-renderer/tests/helper.ts) for how we handle this.
 
 ### Run most tests and linting
 
 ```sh
 cd react_on_rails_pro
-yarn run check
+pnpm run check
 ```
 
 ### Starting the Dummy App
+
 Before running the dummy app,
 you need to generate JavaScript packs in the dummy app project.
 To do this,
@@ -298,15 +314,17 @@ Before running Ruby tests ensure you have done the following steps in `spec/dumm
 
 ```sh
 # in the root directory
+pnpm install -r
+
+cd react_on_rails
 bundle install
-yarn install
 
 cd spec/dummy
 
 bundle install
 bundle exec rake react_on_rails:generate_packs
 
-yarn install
+pnpm install -r
 
 RAILS_ENV=test bin/shakapacker # to generate assets for test environment
 ```
@@ -315,7 +333,7 @@ Then in a separate terminal, run the following to run the Node renderer and the
 
 ```sh
 # in spec/dummy directory
-yarn run node-renderer
+pnpm run node-renderer
 RAILS_ENV=test bin/dev&
 ```
 
@@ -330,6 +348,7 @@ If you run `rspec` at the top level, you'll see this message: `require': cannot
 After running a test, you can view the coverage results in SimpleCov reports by opening `coverage/index.html`.
 
 ### Debugging
+
 Start the sample app like this for some debug printing:
 
 ```sh
@@ -350,6 +369,7 @@ Contact Justin Gordon, [justin@shakacode.com](mailto:justin@shakacode.com) for r
 You need authentication for public package registries:
 
 **Public packages (npmjs.org + rubygems.org):**
+
 - NPM: Run `npm login`
 - RubyGems: Standard credentials via `gem push`
 
@@ -372,5 +392,6 @@ rake release[17.0.0,false,verdaccio]
 ```
 
 For complete documentation, see:
+
 - [Root Release Documentation](../docs/contributor-info/releasing.md)
 - Run `rake -D release` for inline help

data/Gemfile.development_dependencies

@@ -1,13 +1,16 @@
 # Keep in sync with https://github.com/shakacode/react_on_rails/blob/master/Gemfile.development_dependencies
 # frozen_string_literal: true
 
+# Shared dev dependencies (rubocop, etc.)
+eval_gemfile File.expand_path("../Gemfile.shared_dev_dependencies", __dir__)
+
 git_source(:github) { |repo| "https://github.com/#{repo}.git" }
 
 ruby '3.3.7'
 
 gem "react_on_rails", path: "../"
 
-gem "shakapacker", "9.3.0"
+gem "shakapacker", "9.4.0"
 gem "bootsnap", require: false
 gem "rails", "~> 7.1"
 gem "puma", "~> 6"
@@ -51,9 +54,6 @@ group :development, :test do
   gem 'pry-theme' # An easy way to customize Pry colors via theme files
 
   gem "rbs", require: false
-  gem "rubocop", "1.36.0", require: false
-  gem 'rubocop-performance', "1.15.0", require: false
-  gem 'rubocop-rspec', "2.13.2", require: false
   gem "scss_lint", require: false
   gem 'fakefs', require: 'fakefs/safe'
 end

data/Gemfile.loader

@@ -1,19 +1,20 @@
 # frozen_string_literal: true
 
 # Load base dependencies
-base_deps = File.read(File.expand_path("./Gemfile.development_dependencies", __dir__))
+base_deps_path = File.expand_path("./Gemfile.development_dependencies", __dir__)
+base_deps = File.read(base_deps_path)
 
 # Determine which override file to use
-override_deps = if ENV["CI"] == "true" && File.exist?(File.expand_path("./Gemfile.ci", __dir__))
+override_deps_path = if ENV["CI"] == "true" && File.exist?(File.expand_path("./Gemfile.ci", __dir__))
   # In CI environment, use CI dependencies
-  File.read(File.expand_path("./Gemfile.ci", __dir__))
+  File.expand_path("./Gemfile.ci", __dir__)
 elsif File.exist?(File.expand_path("./Gemfile.local", __dir__))
   # In non-CI environment, use local dependencies if they exist
-  File.read(File.expand_path("./Gemfile.local", __dir__))
-else
-  ""
+  File.expand_path("./Gemfile.local", __dir__)
 end
 
+override_deps = override_deps_path ? File.read(override_deps_path) : ""
+
 # Parse override gems
 override_gem_names = override_deps.scan(/^\s*gem\s+["']([^"']+)["']/).flatten
 
@@ -26,7 +27,9 @@ end
 base_deps.gsub!(/^\s*$\n/, '')
 
 # Evaluate the modified base dependencies
-eval(base_deps)
+# Using instance_eval with filepath preserves __dir__ in evaluated content,
+# allowing eval_gemfile calls to work correctly inside loaded files.
+instance_eval(base_deps, base_deps_path)
 
 # Evaluate override dependencies if they exist
-eval(override_deps) unless override_deps.empty?
+instance_eval(override_deps, override_deps_path) unless override_deps.empty?