jsbundling-rails
vite_ruby
jsbundling-rails | vite_ruby | |
---|---|---|
38 | 25 | |
798 | 1,156 | |
1.6% | - | |
6.9 | 6.8 | |
about 1 month ago | 4 days 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.
vite_ruby
- Vite Ruby: Bringing joy to your front end experience
-
Integrating Bun with Vite Ruby for Lightning-Fast Frontend Builds
With the recent release of Bun and its newfound support for Vite, coupled with Ruby on Rails 7.1 incorporating native support for Bun, developers can now enhance their web development workflow significantly. Here is the effortless process of enabling Bun for Vite Ruby, ultimately streamlining your front-end builds.
-
Rails Frontend Bundling - Which one should I choose?
Vite, in particular, ViteRuby is a solid option. It sits between ESBuild and Webpacker, and if you're looking at Webpacker, Vite may actually be a better option for you. It is a very solid option, and I've enjoyed using Vite personally.
- Issues upgrading webpacker v5->6 (intermediate step to shakapacker)
-
All The Rails Asset Pipelines
Yep. vite_rails (website/GitHub) is the way to go.
-
Setting up Svelte with Rails?
Use vite with https://vite-ruby.netlify.app/ if you don’t go the inertia route.
-
Setup Vite on Rails-7
--skip-javascript is necessary for avoiding conflicts on the next steps. In case of bootstrap/foundation-sites the asset pipeline is helpful so --skip-asset-pipeline is not applied.
-
Improve your frontend experience in Ruby with Vite.js;
Vite Ruby is an umbrella project with libraries that will allow you to easily integrate Vite at your favourite Ruby framework, such as Rails or Hanami, or a plain Rack app. If you are tired of waiting for webpack to compile, this project might be for you. Vite.js in Ruby ## Why Vite? 🤔 Vite does not bundle your code during development, which means the dev server is extremely fast to start, and your changes will be updated instantly thanks to HMR. This is great when adjusting styles, or tweaking behavior in JS. In production, Vite bundles your code with tree-shaking, lazy-loading, and common chunk splitting out of the box, to achieve optimal loading performance. ## Why Vite in Ruby? 🤔 Vite is great on its own, but configuring it correctly to work for a Ruby app structure requires knowledge of its internals. By following existing Rails and Rack conventions, and adding a few of its own, it becomes possible for ⠀everyone to leverage Vite and its wonderful features! If you are curious about the difference, check this Jumpstart Rails template.
-
Webpacker Retired
Vite Rails Docs
-
Autoreloading htmls in Browser with Rails 7
It something that basically doesn't work properly since the birth of Rails, 15 years ago. For beginners, this is a big disappointment. You have to tweak Guard-livereload (tricky and not always working, as you mentionned), or try things like browserSync (also tricky, also not always working...) My advice so far : keep Sprockets, in order to have a nice integration with older gems. And completly remove the current js-bundling + importmaps. Instead, replace with the gem 'vite_rails' (repo here : https://github.com/ElMassimo/vite_ruby).
What are some alternatives?
importmap-rails - Use ESM with importmap to manage modern JavaScript in Rails without transpiling or bundling.
hotwire-rails - Use Hotwire in your Ruby on Rails app
docker-rails-example - A production ready example Rails app that's using Docker and Docker Compose.
esbuild-live-reload
esbuild-rails - Esbuild Rails plugin
Webpacker - Use Webpack to manage app-like JavaScript modules in Rails
esbuild - An extremely fast bundler for the web
vite_rails - ⚡️ Vite.js in Ruby, bringing joy to your JavaScript experience [Moved to: https://github.com/ElMassimo/vite_ruby]
shakapacker - Use Webpack to manage app-like JavaScript modules in Rails
Tailwind CSS - A utility-first CSS framework for rapid UI development.