jsbundling-rails
hotwire-rails
Our great sponsors
jsbundling-rails | hotwire-rails | |
---|---|---|
38 | 98 | |
795 | 960 | |
2.3% | - | |
6.9 | 3.2 | |
about 1 month ago | over 2 years ago | |
Ruby | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jsbundling-rails
- Rails Merging Support for Bun.sh
- Rails Frontend Bundling - Which one should I choose?
-
Is the default importmap method unrealistic in the most popular real world use cases?
I think this is more like a demo - you will not get the same features as jsbundling-rails by only following instructions in the video. For that you will need to change some other files as well. You can find out what files to be added/changed from the install script. The important bits are mostly the same as in the video, but some supplement parts are not mentioned in the video. Some people actually reported in the comment that they can't deploy such app, but I think it depends.
-
at my wits' end.. please help me figure out why javascript won't work (Rails 7 with esbuild)
I'm sorry, I didn't see that in your title. Using esbuild is 100% supported by Rails through this gem https://github.com/rails/jsbundling-rails. Have a look at the docs there to make sure that you're setup correctly.
-
Configure Stimulus with esbuild and Babel — Rails & Javascript
Rails applications are bundler-agnostic. They do not care how you bundle your javascript code. It just expects whatever comes from the bundler to be placed under app/assets, so the asset pipeline processes it. We can see this in the official jsbundling-rails gem, which consists of scripts to install different bundlers and configure a default npm build command to generate our bundles—no interaction whatsoever with the Rails configuration. This black-box bundler logic allows us to change and update our bundler system without tuning any other aspect of our Rails application.
-
foreman: not found
Hello, this is my first time setting up a rails app that also uses react, I am using https://github.com/rails/jsbundling-rails I went with esbuild because I am following this tutorial on setting it up https://www.youtube.com/watch?v=yoLJXjEV2nM, however when I run bin/dev in the terminal I get the error bin/dev: 8: exec: foreman: not found
- Ruby 3.2 + Rails 7 + Tailwind + Font Awesome - should be blazing fast, yet tests very slow. 20 requests are being made. How do I make fewer requests, create fewer objects and make this simple app super fast? Production : https pickaxe dot ca. Thank you! -Dan H
-
How to bundle assets in a Rails engine
You first install your asset handlers as you need them for your project. They can be anything from rails/jsbundling-rails and rails/tailwindcss-rails to webpacker or something custom.
-
Comparing Phoenix to Rails in December 2022
The functionality comes from https://github.com/rails/jsbundling-rails and https://github.com/rails/cssbundling-rails -- both come with Rails 7 and all you have to do is generate your app with the choices you want such as -j esbuild --css tailwind.
-
Vercel announces Turbopack, the successor to Webpack
The Rails https://github.com/rails/jsbundling-rails gem lets you pick between esbuild, rollup and Webpack. If Turbopack ends up being popular then jsbundling should be able to support it.
The nice thing about Rails now is there's no direct integration like Webpacker once was. Now we can basically use the JS tool straight up and Rails will just look at assets in a specific directory, it doesn't matter what tool generated it.
hotwire-rails
- It's not Ruby that's slow, it's your database
- Howire Not Working after deploying to Heroku
-
What's New in Rails 7
Applications generated with Rails 7 will get Turbo and Stimulus (from Hotwire) by default, instead of Turbolinks and UJS. Hotwire is a new approach that delivers fast updates to the DOM by sending HTML over the wire.
-
Ask HN: What tech stack would you use to build a new web app today?
For Ajax-y stuff, I am really excited by the new crop of "HTML-as-a-Service" or "HTML-over-the-wire."
https://htmx.org/
https://hotwired.dev/
- Ask HN: Do we need JavaScript web frameworks?
-
anyone have full tutorial how to upgrade from rails 6.1 to rails 7 ?
For all the turbo/stimulus/hotwire mix, you want to add a new feature just for the sake of adding it? or do you have a use case that fits the feature? if you have then you probably already have an implementation with a different technology (stimulus reflex? some custom websockets or ajax implementation? something with anycable?) and you have to check how to migrate from that technology to hotwire. If you just want to use the feature with no real need for it to practice then just pick any tutorial from the internet (like the intro in the official website https://hotwired.dev).
-
Ask HN: What are you favorite goto frameworks when writing Web Aplications
I was recently interested in similar topic. Here are 3 similar solutions I found:
* https://htmx.org/
* https://unpoly.com/
* https://hotwired.dev/
My personal preference is Unpoly (the idea of "layers" is awesome). But the best explanation of concept as a whole (HATEOAS, keeping app state on server using partial page updates, etc) is at HTMX homepage, and in these essays:
* https://htmx.org/essays/hateoas/
* https://htmx.org/essays/locality-of-behaviour/
-
Hotwire isn't only for Rails
At the end of 2020 the Basecamp team released a collection of Javascript libraries called Hotwire. Modern web stacks have popularized javascript-rendered front ends and JSON transmissions. Hotwire's primary motivation is to reduce the Javascript footprint and allow application front ends to be created in primarily HTML. It pairs very nicely with the Ruby on Rails ideology and is often demonstrated in that context. I aim to write a series on how Hotwire can be used in any application to simplify development and reduce the need for heavy Javascript downloads. Hotwire currently consists of two javascript libraries: Turbo and Stimulus. The first part of this series introduces Turbo.
-
How do you handle views?
I've been doing that a while until I just got sock of the JS spagetti and often duplicated code and went full on Angular CSR and never looked back. That being said, I've been seeing a lot recently about Laravel's Livewire and Symfony and Ruby on Rail's integration with Hotwire (stimulus+turbo).
- Why learn Rails as a frontender?
What are some alternatives?
importmap-rails - Use ESM with importmap to manage modern JavaScript in Rails without transpiling or bundling.
htmx - </> htmx - high power tools for HTML
vite_ruby - ⚡️ Vite.js in Ruby, bringing joy to your JavaScript experience
SvelteKit - web development, streamlined
esbuild-live-reload
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
Webpacker - Use Webpack to manage app-like JavaScript modules in Rails
Svelte - Cybernetically enhanced web apps
esbuild - An extremely fast bundler for the web
phoenix_live_view - Rich, real-time user experiences with server-rendered HTML
shakapacker - Use Webpack to manage app-like JavaScript modules in Rails
inertia-laravel - The Laravel adapter for Inertia.js.