You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

No actionable comments were generated in the recent review. 🎉

Walkthrough

This PR updates many documentation hyperlinks and in-code help/error message URLs across OSS docs, Ruby code, and tests—replacing legacy GitHub wiki and stale links with canonical reactonrails.com docs paths and corrected relative links; small JSDoc and Slack invite fixes included. (≤50 words)

Changes

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• Update Pro docs URL to canonical /docs/pro path #2657 — Makes similar documentation URL updates in the same Ruby files and specs; strong overlap in edited strings.
• Consolidate Pro docs into docs/pro and remove legacy GitBook config #2556 — Overlapping edits consolidating Pro doc links to the canonical docs site.

Poem

🐰 I hopped through docs at break of dawn,

Swapped old links for paths now drawn.
Breadcrumbs tidy, pages bright,
I left the docs a cleaner sight.
🥕✨

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Greptile Summary

This PR is a focused documentation hygiene pass that aligns all in-repo links, runtime error messages, and user-facing help output with the current docs routing structure on reactonrails.com.\n\nKey changes:\n- URL modernisation in Ruby runtime output — five stale /docs/guides/... URLs in doctor.rb, packs_generator.rb, configuration.rb, packer_utils.rb, server_rendering_js_code.rb, and the Rake task are replaced with current reactonrails.com/docs/core-concepts/... and reactonrails.com/docs/configuration/ routes.\n- Pro docs pointer — docs/pro/react-on-rails-pro.md references in AGENTS_USER_GUIDE.md and several OSS docs are updated to docs/pro/home-pro.md, which exists in the repository.\n- React 18+ accuracy — rails-view-rendering-from-inline-javascript.md now correctly documents that ReactOnRails.render returns a React root under React 18+ (not a virtual DOM element), and the jQuery example is updated to call render() on each change rather than the incompatible setState.\n- Dead-link fixes — the docs/README.md changelog link pointed to a non-existent docs/oss/upgrading/changelog.md; it now resolves to the canonical CHANGELOG.md on GitHub. Legacy GitHub wiki links are replaced with reactonrails.com/docs/pro/.\n- Slack invite URL — three docs pages updated from reactrails.slack.com to invite.reactrails.com.\n- Test spec parity — packs_generator_spec.rb updated to match the new URLs in production error messages.

Confidence Score: 5/5

Safe to merge — all changes are documentation and string literals in error messages; no logic is modified.

Every changed Ruby file touches only string literals (URLs in error/help messages). All target paths were verified to exist in the repository or on the canonical docs site. The test spec was updated in lockstep with production code. The one P2 comment (relative path in a code-block comment) is a non-blocking style suggestion.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User encounters error / reads docs] --> B{Source}
    B -->|Runtime Ruby error| C["packs_generator.rb / configuration.rb\npacker_utils.rb / server_rendering_js_code.rb"]
    B -->|rails react_on_rails:doctor| D["doctor.rb help output"]
    B -->|OSS Markdown docs| E["docs/oss/**/*.md"]
    B -->|AGENTS_USER_GUIDE / CHANGELOG| F["Repo-root docs"]

    C -->|old: /docs/guides/...| G["❌ Stale URL (404)"]
    C -->|new: /docs/core-concepts/...| H["✅ Current docs route"]

    D -->|old: /docs/guides/configuration/| I["❌ Stale URL"]
    D -->|new: /docs/configuration/| J["✅ Current docs route"]

    E -->|old: github.com/...wiki| K["❌ Legacy wiki redirect"]
    E -->|new: reactonrails.com/docs/pro/| L["✅ Pro docs landing"]

    E -->|old: reactrails.slack.com| M["❌ Stale Slack URL"]
    E -->|new: invite.reactrails.com| N["✅ Invite link"]

_{Reviews (1): Last reviewed commit: "docs: avoid overlap with active docs PRs" | Re-trigger Greptile}

Review: Docs link alignment pass

Overall this is a clean, low-risk documentation PR. The URL/path updates all check out — I verified the target paths exist on disk and the new URLs match the current docs routing structure. A few observations:

One formatting regression

CHANGELOG.md line 228 — The See the [React on Rails Pro Configuration docs]... sentence was previously indented 2 spaces, making it a continuation paragraph of the - **Pro-Specific Configurations Moved to Pro Gem** list item. Removing the indent breaks it out of the list, producing an orphaned paragraph between two bullet items. See the inline comment for a one-line fix.

Notes (no action required)

• docs/README.md changelog link — swapping ./oss/upgrading/changelog.md for the GitHub URL is reasonable; the two files are byte-for-byte identical, so the only practical difference is that readers land on GitHub rather than the rendered docs site.
• React 18 return-value docs (rails-view-rendering-from-inline-javascript.md) — the update from component.setState(...) to a re-render call is a correct React 18 fix; setState is not available on React roots.
• Ruby comment paths (e.g., docs/oss/configuration/README.md) — these are inside code blocks so they won't render as hyperlinks in any viewer; the relative path change is still accurate.
• docs/pro/react-on-rails-pro.md → home-pro.md — both files exist; home-pro.md appears to be the current landing page.

Outside of the CHANGELOG indentation fix this looks good to merge.

Review: docs: fix stale docs links and help URLs

Overall a clean, well-scoped maintenance pass. All link targets were verified.

What looks good:

• URL targets are correct: docs/pro/home-pro.md exists, the relative path ../upgrading/release-notes/16.0.0.md resolves correctly from docs/oss/configuration/, and docs/oss/upgrading/upgrading-react-on-rails.md exists.
• jQuery example fix is correct and important: The old pattern called component.setState() on the return value, which silently breaks under React 18+ since createRoot returns a root object, not a component instance. Re-calling ReactOnRails.render is the right approach.
• Slack URL: Switching from reactrails.slack.com to invite.reactrails.com is the right choice for public documentation.
• JSDoc URL updated from http://usejsdoc.org/ to https://jsdoc.app/ is correct.
• Spec file updated in sync: Expected error messages in packs_generator_spec.rb match the new URLs.

Minor note:
In docs/oss/building-features/how-to-conditionally-server-render-based-on-device-type.md, the new link is inside a Ruby code block comment. Relative Markdown links inside fenced code blocks do not render as hyperlinks, so readers see the raw string. The old absolute GitHub URL was at least navigable if someone copied the snippet. Not a blocker.

Verdict: No security concerns, no broken paths, no logic errors. Ready to merge.

Review Summary

This is a clean, well-scoped docs cleanup pass. Changes are limited to link updates and documentation accuracy improvements with no functional behavior changes. The spec file is correctly updated to match new error message URLs.

Positive changes:

• Replacing component.setState() with renderComponent() in the inline JS example is the right fix — calling setState externally is an anti-pattern that does not work with React 18+ functional components or hooks.
• Slack invite URL update (reactrails.slack.com to invite.reactrails.com) and JSDoc domain update (usejsdoc.org to jsdoc.app) are correct.
• All URL path migrations from /docs/guides/ to /docs/core-concepts/, /docs/configuration/, and /docs/upgrading/ look consistent and correct.
• The relative link ../upgrading/release-notes/16.0.0.md in docs/oss/configuration/README.md resolves correctly.

Minor issue (inline comment posted):
The ReactDOM.render reference in the JSDoc 'Does this:' comment is the old React 16/17 API — it is slightly misleading now that the surrounding text correctly describes React 18+ returning a createRoot root object.

Verdict: Looks good with one minor suggestion.

Review: docs: fix stale docs links and help URLs

Overall: LGTM — clean, well-scoped docs cleanup. All link targets verified against the repo tree; spec fixtures correctly mirror the updated error messages in production code.

What looks good

• All five URL path changes in Ruby source (configuration.rb, doctor.rb, packer_utils.rb, packs_generator.rb, server_rendering_js_code.rb) move from stale /guides/ and /guides/file-system-based-* URLs to real published routes, and the corresponding spec fixture strings in packs_generator_spec.rb are updated to match — no test/prod divergence.
• Replacing component.setState({ value }) with a re-render call is the right correction for React 18+ where ReactDOM.createRoot(...).render() returns a Root object, not a component instance.
• The Slack invite URL swap (reactrails.slack.com → invite.reactrails.com) and JSDoc domain fix (usejsdoc.org → jsdoc.app) are straightforward and correct.
• Relative-path internal links (../configuration/README.md, ../upgrading/release-notes/16.0.0.md) both resolve to existing files in the tree.

One minor nit

In rails-view-rendering-from-inline-javascript.md, the updated top-level description and @returns JSDoc now accurately describe React 18+ vs 16/17 return values, but the inner block comment still says:

 * Does this:
 *   ReactDOM.render(React.createElement(HelloWorldApp, {name: "Stranger"}),
 *     document.getElementById('app'))

ReactDOM.render() is the legacy React 16/17 API (deprecated in React 18). Since the file now explicitly discusses React 18+ roots, this comment can mislead readers into thinking ReactOnRails still calls the legacy API internally. Consider noting that under React 18+ it uses ReactDOM.createRoot(el).render(), or simply remove the "Does this:" block since the surrounding text already covers the semantics.

This is non-blocking — the functional behavior of the example is correct regardless.

Review: #2850

Overall the link-cleanup work here is solid — the URL migrations from the old GitHub wiki and stale /docs/guides/ paths to the correct canonical routes are accurate, the relative-link fix in docs/oss/configuration/README.md resolves correctly, and the test expectations in packs_generator_spec.rb were updated to match the new error-message URLs.

One factual inaccuracy in the new API docs (see inline comment):

The paragraph added to docs/oss/api-reference/rails-view-rendering-from-inline-javascript.md:

ReactOnRails.render skips duplicate renders for the same connected node, so calling it repeatedly on #root will be ignored unless that node is replaced first.

This is not supported by the code. The public ReactOnRails.render method in packages/react-on-rails/src/base/client.ts calls reactHydrateOrRender unconditionally — there is no deduplication guard there. The skip logic only lives in the internal renderElement function inside ClientRenderer.ts, which is used by the page-lifecycle path (renderAllComponents / renderComponent), not by the public API. Calling the public ReactOnRails.render twice on the same node will create a second root (React 18+) or trigger a second legacy render — it is not silently ignored.

Everything else looks good:

• URL replacements (wiki → reactonrails.com, old /guides/ → correct segment, Slack join → invite link, usejsdoc.org → jsdoc.app) all check out.
• The React 18+ vs 16/17 return-value clarification in the @returns JSDoc is accurate (verified against reactApis.cts).
• Removing the jQuery setState example is correct — ReactDOM.render's return value had a setState under React 16/17 class components, but the root object returned by React 18 does not.
• The docs/pro/home-pro.md target exists; react-on-rails-pro.md is also still present so old deep-links won't break immediately, but keeping home-pro.md as the primary target is appropriate.

Addressed the remaining actionable review feedback on this PR.

• Updated docs/oss/api-reference/rails-view-rendering-from-inline-javascript.md in 8f028708 to correct the React 16/17 return-value wording and the guidance about repeated ReactOnRails.render calls.
• The other still-open inline doc threads were already stale on-branch and are being resolved as already handled.

Review

Overall: LGTM with one minor inconsistency to fix.

This is a clean, low-risk docs pass. All the URL updates are correct:

• Old wiki links (github.com/shakacode/react_on_rails/wiki) → reactonrails.com/docs/pro/
• Old /guides/ path prefix → current path structure (/core-concepts/, /configuration/, /upgrading/)
• Stale .md file extensions removed from runtime-message URLs (avoids 404s on the live docs site)
• reactrails.slack.com → invite.reactrails.com ✓
• usejsdoc.org → jsdoc.app ✓

Verified:

• docs/pro/home-pro.md exists — the AGENTS_USER_GUIDE.md and generator-details.md links are valid
• docs/oss/upgrading/release-notes/16.0.0.md exists — the configuration/README.md relative link fix is correct
• No remaining /guides/ URLs in the Ruby lib files
• Spec expectations updated in sync with the Ruby error message changes ✓

One issue flagged inline: rails-view-rendering-from-inline-javascript.md still uses jQuery ($('#input'), .val()) in the code example even though the prose was updated to remove the jQuery framing. A vanilla JS equivalent would align the example with the new narrative.

Review

This is a clean, well-scoped docs pass. All the URL migrations check out and I verified the key technical claims.

Verified correct:

• All /guides/ → current path structure (/core-concepts/, /configuration/, /upgrading/) changes are accurate
• Old GitHub wiki Pro links → reactonrails.com/docs/pro/ ✓
• reactrails.slack.com → invite.reactrails.com ✓
• usejsdoc.org → jsdoc.app ✓
• docs/pro/home-pro.md exists; react-on-rails-pro.md is also still present so old deep-links remain valid ✓
• Relative link fix in docs/oss/configuration/README.md: ../upgrading/release-notes/16.0.0.md resolves correctly ✓
• Spec expectations in packs_generator_spec.rb updated in sync with Ruby error message URL changes ✓

On the deduplication statement (re: CodeRabbit's open request-for-changes): the current wording — "The public ReactOnRails.render API does not deduplicate repeated calls" — is factually correct. Traced the call path: base/client.ts#render → reactHydrateOrRender → reactRender/reactHydrate with no guard. The deduplication via renderedRoots.get(domNodeId) lives only in the internal renderElement function in ClientRenderer.ts (the page-lifecycle path), not in the public API. CodeRabbit's suggestion to say it does deduplicate would be inaccurate.

One minor notation nit left inline (CSS selector #root vs bare id string 'root'). Otherwise LGTM.