Problem
After #2284 (and follow-up compatibility work in #2424), there are now two real-world webpack export shapes in existing Pro apps:
- legacy:
module.exports = configureServer
- current:
module.exports = { default: configureServer, extractLoader }
The standalone rails g react_on_rails:rsc path now supports both, but docs still read as if everyone is on the latest shape.
Proposal
Add a dedicated docs section: "Upgrading an Existing React on Rails Pro App to RSC".
Suggested content:
- Prerequisites and version checks (React 19.0.x, Pro installed).
- Runbook for standalone
react_on_rails:rsc usage.
- What files are expected to change.
- Compatibility note for legacy
serverWebpackConfig.js export style.
- How to verify success (
rsc-bundle, route check, page render check).
Acceptance Criteria
Problem
After #2284 (and follow-up compatibility work in #2424), there are now two real-world webpack export shapes in existing Pro apps:
module.exports = configureServermodule.exports = { default: configureServer, extractLoader }The standalone
rails g react_on_rails:rscpath now supports both, but docs still read as if everyone is on the latest shape.Proposal
Add a dedicated docs section: "Upgrading an Existing React on Rails Pro App to RSC".
Suggested content:
react_on_rails:rscusage.serverWebpackConfig.jsexport style.rsc-bundle, route check, page render check).Acceptance Criteria