You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why do both the documentation and templates for React Router 7 seem to enforce the use of TypeScript?
Considering that React Router 7 appears to be inspired by legacy SPAs, many of which are built with plain JavaScript, this approach seems inconsistent. A significant number of legacy React SPAs still use JavaScript rather than TypeScript.
Shouldn't the React Router CLI and documentation offer clear options for choosing between JavaScript and Typescript, rather than defaulting to or heavily emphasizing only TypeScript?
The text was updated successfully, but these errors were encountered:
wanGiB
changed the title
Should React Router 7 Provide Better Support for JavaScript Users?
Shouldn't React Router 7 Provide Better Support for JavaScript Users?
Nov 24, 2024
Why do both the documentation and templates for React Router 7 seem to enforce the use of TypeScript?
Considering that React Router 7 appears to be inspired by legacy SPAs, many of which are built with plain JavaScript, this approach seems inconsistent. A significant number of legacy React SPAs still use JavaScript rather than TypeScript.
Shouldn't the React Router CLI and documentation offer clear options for choosing between JavaScript and Typescript, rather than defaulting to or heavily emphasizing only TypeScript?
The text was updated successfully, but these errors were encountered: