Fix TypeScript import errors in RSCRoute and RSCProvider

[justin808]

Summary

Fix TypeScript import errors in the Pro package's RSCRoute.tsx and RSCProvider.tsx files.

Details

The TypeScript imports in these files have errors that need to be corrected for proper type checking and IDE support.

Related Branch

This fix was identified in the justin808/shakapacker-9.3.0 branch (commit acbb195).

Impact

• Fixes TypeScript compilation errors
• Improves IDE support and developer experience
• No runtime behavior changes

Files Changed

• packages/react-on-rails-pro/src/RSCProvider.tsx
• packages/react-on-rails-pro/src/RSCRoute.tsx

Total: 6 lines changed (2 insertions, 6 deletions)

Labels

• Bug
• TypeScript
• Pro

[coderabbitai]

A summary of the changes CodeRabbit can apply:

• Update Pro package TypeScript files to fix import/type errors by adding import type { ReactNode } and replacing React.ReactNode with ReactNode in RSCProvider.tsx (done) and RSCRoute.tsx (done except remove duplicate ServerComponentFetchError import at line 21 and delete the 'use client'; directive).

• Update RSCProvider.tsx and RSCRoute.tsx to replace inline React.ReactNode types with a top-level imported type alias (import type { ReactNode } from 'react'), update promises/records and component signatures to use ReactNode, adjust RSCRoute error-boundary and PromiseWrapper prop typings accordingly, and remove the 'use client' directive.

• ✅ Create PR with these edits
• 📋 Get copyable edits

[justin808]

This issue is already resolved on the master branch. The files packages/react-on-rails-pro/src/RSCProvider.tsx and packages/react-on-rails-pro/src/RSCRoute.tsx already have the correct imports (import * as React from 'react') and do not have the problematic import ReactClient from 'react/index.js' pattern.

The fix was identified in the justin808/shakapacker-9.3.0 branch (commit acbb195), but the master branch never had this issue because when the Pro package was first created in PR #1841 (commit 7bce94a), it already used the correct import pattern.

The problematic imports were only introduced temporarily in the justin808/shakapacker-9.3.0 branch as part of React 19 compatibility work and have been fixed there.

Status: No action needed - master is already correct.