importmap-rails
vite_ruby
Our great sponsors
importmap-rails | vite_ruby | |
---|---|---|
25 | 25 | |
1,007 | 1,146 | |
2.0% | - | |
8.2 | 7.1 | |
about 2 months ago | 8 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.
importmap-rails
-
RubyJS-Vite
With importmaps (https://github.com/rails/importmap-rails) and Hotwire (https://hotwired.dev/), you write plain js and serve it.
Also packages are served via CDN. There is no tree shaking. Rails got rid of the whole bundling step.
-
First commits in a Ruby on Rails app
Importmap audit - “checks the NPM registry for known security issues”
-
Asset compilation taking ~ 12 mins
It worked, but JS changes were not coming through. Digging into the Importmap docs (see 'sweeping the cache', it monitors changes according to the setting config.importmap.cache_sweepers. So, by adding the locations where I have my JS files, I also got JS changes passed through.
-
Is the default importmap method unrealistic in the most popular real world use cases?
You can't use TypeScript, or anything that requires pre-compile, with importmap. answered issue
-
Ruby on Rails with React on Typescript using importmaps
Let's begin by installing the necessary dependencies. The first gem generates the importmap object, manages caching, and helps with library installations, among other things. I recommend reading the entire readme to become familiar with its capabilities. The second gem will be discussed later, it is used to compile JSX files. Gemfile
-
Pirep.io collects the unpublished, local knowledge on public, private, and unmapped airport that anyone can contribute to
Yeah, those were brand new right around the time I started this project a few years ago with Rails 7 (or was it 6.1?). I actually ended up removing them in favor of importmap-rails since I wanted as simple of a frontend as possible and I wasn't sure of relying on what was, at the time, a brand new way of doing frontend work. Things change so quickly in JS-land that I'm always hesitant to make something a dependency unless it has a strong track record of being continuously maintained.
-
Dusting off my rails knowledge, need some tips / guidance on rails 7 and production
source "https://rubygems.org" git_source(:github) { |repo| "https://github.com/#{repo}.git" } ruby "3.1.0" # Bundle edge Rails instead: gem "rails", github: "rails/rails", branch: "main" gem "rails", "~> 7.0.4", ">= 7.0.4.2" # The original asset pipeline for Rails [https://github.com/rails/sprockets-rails] gem "sprockets-rails" # Use sqlite3 as the database for Active Record gem "sqlite3", "~> 1.4" # Use the Puma web server [https://github.com/puma/puma] gem "puma", "~> 5.0" # Use JavaScript with ESM import maps [https://github.com/rails/importmap-rails] gem "importmap-rails" # Hotwire's SPA-like page accelerator [https://turbo.hotwired.dev] gem "turbo-rails" # Hotwire's modest JavaScript framework [https://stimulus.hotwired.dev] gem "stimulus-rails" # Build JSON APIs with ease [https://github.com/rails/jbuilder] gem "jbuilder" gem "mongoid" gem "mongoid-grid_fs" gem 'bootstrap', '~> 5.2.2' #sourced from https://github.com/twbs/bootstrap-rubygem gem 'rack-cors' # Windows does not include zoneinfo files, so bundle the tzinfo-data gem gem "tzinfo-data", platforms: %i[ mingw mswin x64_mingw jruby ] # Reduces boot times through caching; required in config/boot.rb gem "bootsnap", require: false
- Simple Modern JavaScript Using JavaScript Modules and Import Maps
-
A powerful search feature with what Rails provides out of the box
Also, installing StimulusReflex seems quite not easy for the moment: It seems there are some quirks along the way if you're using import-maps for managing javascript dependencies as I do. Embracing the Rails way at least prevents you from this sort of issue.
-
Stimulus MultiSelect
If you're using importmap-rails, you'll need to pin stimulus-multiselect:
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?
jsbundling-rails - Bundle and transpile JavaScript in Rails with esbuild, rollup.js, or Webpack.
esbuild-rails - Esbuild Rails plugin
docker-rails-example - A production ready example Rails app that's using Docker and Docker Compose.
esbuilder - Integrate esbuild into Rails
esbuild-live-reload
Webpacker - Use Webpack to manage app-like JavaScript modules in Rails
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
vite_rails - ⚡️ Vite.js in Ruby, bringing joy to your JavaScript experience [Moved to: https://github.com/ElMassimo/vite_ruby]
sprockets-rails - Sprockets Rails integration
Tailwind CSS - A utility-first CSS framework for rapid UI development.