Flip shakapacker back to rspack once react_on_rails_rsc#29 ships rspack RSC support
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, react, webpack
- Domain
- build-system, frontend
Research direction
After react_on_rails_rsc#29 ships, run the specified git grep command at merge commit 2f7d3330 across config/, Procfile.dev, and README.md. Verify each replacement against the upstream published API, then redeploy the review app and manually check /server-components: all four sections render, RSC payloads stream, and the Refresh, Simulate Error, and Retry flow has no page-shift artifacts.
Written by the indexing model from the issue text.
Description
#727 (Pro RSC migration) tactically reversed this repo's bundler from rspack to webpack because react-on-rails-rsc/WebpackPlugin (used by the RSC bundle build) requires webpack APIs that rspack 2.0.0-beta.7's compatibility layer doesn't cover. The reversal is tracked by a TODO in config/shakapacker.yml.
Once shakacode/react_on_rails_rsc#29 ships its RSCRspackPlugin (rspack-native parallel to RSCWebpackPlugin), this repo should flip back: webpack → rspack throughout. The exact import paths, export names, and any companion loader APIs should be taken from upstream's published surface at the time of the flip, not from this issue.
Starting point for the agent picking this up: git grep -nE "webpack|WebpackPlugin|WebpackLoader|@rspack|rspack" config/ Procfile.dev README.md against the merge commit of #727 (2f7d3330) — that surfaces every place affected by the temporary state. Verify each replacement against the published upstream API at flip time.
Verification after flipping: redeploy review-app + manual QA on /server-components (all four sections render, RSC payloads stream, Refresh / Simulate Error / Retry flow works without page-shift artifacts).
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 370
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from shakacode/react-webpack-rails-tutorial
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 50/100
-
question
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 28/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in shakacode/react-webpack-rails-tutorial
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
babalae/bettergi-scripts-list#3674 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vadimdemedes/ink#1029 ·
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·