rails_panel
vite_ruby
Our great sponsors
rails_panel | vite_ruby | |
---|---|---|
3 | 25 | |
3,829 | 1,151 | |
- | - | |
0.0 | 6.8 | |
15 days ago | 12 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.
rails_panel
-
RoR Debugbar
This seems pretty similar to https://github.com/dejan/rails_panel. Was that your inspiration?
-
Why do my requests take so much time to complete when View and ActiveRecord are finishing fast?
There's a few things that could be happening. I recommend trying out https://github.com/dejan/rails_panel. It gives you a better break down if exactly what's taking time. You also might look at how long it takes to actually instantiate your models. The actual query time is usually the slowest operation, but if you have a bunch of models on the page just the classes being loaded can take a good amount of time
-
Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup
Love seeing the set of gems that folks tend to bring into all their projects. https://github.com/dejan/rails_panel Was a new one for me, will def be checking that out
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?
docker-rails-example - A production ready example Rails app that's using Docker and Docker Compose.
importmap-rails - Use ESM with importmap to manage modern JavaScript in Rails without transpiling or bundling.
jsbundling-rails - Bundle and transpile JavaScript in Rails with esbuild, rollup.js, or Webpack.
esbuilder - Integrate esbuild into Rails
Doorkeeper - Doorkeeper is an OAuth 2 provider for Ruby on Rails / Grape.
esbuild-rails - Esbuild Rails plugin
stackprof - a sampling call-stack profiler for ruby 2.2+
Webpacker - Use Webpack to manage app-like JavaScript modules in Rails
ransack - Object-based searching.
vite_rails - ⚡️ Vite.js in Ruby, bringing joy to your JavaScript experience [Moved to: https://github.com/ElMassimo/vite_ruby]