> Later in the year, Rails retired Webpacker
Is Rails anti Typescript? It’s weird to see most other JS environments move to Typescript by default, while Rails now now ignores the ability to use it without jumping through hoops.
Is Rails anti Typescript? It’s weird to see most other JS environments move to Typescript by default, while Rails now now ignores the ability to use it without jumping through hoops.
But if you plan to support multiple targets (web, mobile, headless) then you have to develop an api anyway so why not use the best front end framework for each of your targets?
Rails doesn't stop you from building a backend for your React and React Native frontends, for example just look at Shopify.
Have you not paid attention to the direction Rails is going? Hotwire (Rails' default front end) is all amount rendering HTML directly (not via JS) and using the absolute bare minimum amount of vanilla Javascript (with Stimulus). It's not React... So why would it need TypeScript's features and added complexity?
The whole point is using vanilla ES6 without a compilation step...
You can use Rails with React/Vue + TypeScript pretty easily by using something like rails-esbuild or vite_ruby.
I'm currently working on a project with Rails, React, TypeScript, Vite, and InertiaJS and have been very much enjoying it, especially now that Inertia supports SSR.