-
turbo
The speed of a single-page web application without having to write any JavaScript (by hotwired)
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
inertia
Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Foundation
The most advanced responsive front-end framework in the world. Quickly create prototypes and production code for sites that work on any kind of device.
-
Bootstrap
The most popular HTML, CSS, and JavaScript framework for developing responsive, mobile first projects on the web.
This bundle of tutorials is bringing together Rails-7, Vite, Inertia, Svelte, Stimulus, Turbo, and: Bootstrap or Foundation-Sites.
This bundle of tutorials is bringing together Rails-7, Vite, Inertia, Svelte, Stimulus, Turbo, and: Bootstrap or Foundation-Sites.
I spent weeks for understanding all that new frontend options around the new rails-7 and the great new enhancements. From my view, rails should only have two default options on frontend: Importmaps, which needs no Node setup on development machine and production server. But, if you have Node or you want to have Hot Module Reloading (HMR) with code-splitting or want or have to be able compiling javascript files like .ts, .jsx, .svelte. So, if Node, why not Vite? I totally agree with Juice10. Currently Webpacker has more Downloads but reading comparitions it seems to be a matter of time until Vite is ahead. On the other hand, jsbundling together with a gem like rails_live_reload is working fast, but its always triggering a page reload and all the javascript even if you're just modifying styles. This was the decisive reason for me.
I spent weeks for understanding all that new frontend options around the new rails-7 and the great new enhancements. From my view, rails should only have two default options on frontend: Importmaps, which needs no Node setup on development machine and production server. But, if you have Node or you want to have Hot Module Reloading (HMR) with code-splitting or want or have to be able compiling javascript files like .ts, .jsx, .svelte. So, if Node, why not Vite? I totally agree with Juice10. Currently Webpacker has more Downloads but reading comparitions it seems to be a matter of time until Vite is ahead. On the other hand, jsbundling together with a gem like rails_live_reload is working fast, but its always triggering a page reload and all the javascript even if you're just modifying styles. This was the decisive reason for me.
This bundle of tutorials is bringing together Rails-7, Vite, Inertia, Svelte, Stimulus, Turbo, and: Bootstrap or Foundation-Sites.
This bundle of tutorials is bringing together Rails-7, Vite, Inertia, Svelte, Stimulus, Turbo, and: Bootstrap or Foundation-Sites.
This bundle of tutorials is bringing together Rails-7, Vite, Inertia, Svelte, Stimulus, Turbo, and: Bootstrap or Foundation-Sites.
Views are written in haml. If you work on erb there are converters like haml-to-erb. I am working on RubyMine, Apple-Notebook, production Server is Debian (for node-setup) and yarn. I tried to write less text and rather link to the sources.
This bundle of tutorials is bringing together Rails-7, Vite, Inertia, Svelte, Stimulus, Turbo, and: Bootstrap or Foundation-Sites.
This bundle of tutorials is bringing together Rails-7, Vite, Inertia, Svelte, Stimulus, Turbo, and: Bootstrap or Foundation-Sites.