jsbundling-rails
propshaft
jsbundling-rails | propshaft | |
---|---|---|
38 | 11 | |
798 | 814 | |
1.6% | 2.1% | |
6.9 | 6.8 | |
about 1 month ago | 16 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.
propshaft
-
The Full-Stack development experience
Ruby On Rails, thanks to propshaft, closes a chapter. Welcome to 2023, where deploying JavaScript and CSS is a breeze. Welcome to the no-build era.
-
A Quick and Easy Guide to the Asset Pipeline in Rails 7
No mention of propshaft which is the true replacement for sprockets: https://github.com/rails/propshaft
-
Gnarly Learnings From June 2022
Learning about new ways to manipulate data in Ruby is always fun. This article details a way to access hash values as if they were methods via the ActiveSupport::OrderedOptions class. Initially, it wasn't clear why someone would reach for this over the default syntax, but the author pointed out that syntax can be helpful in keeping configuration files clean and readable. Apparently, this can be observed in the wild in the Propshaft (an asset pipeline library) codebase, which uses it to define config.assets in Railtie.
- How to use Bootstrap 5 in Rails 7 - Importmaps & Sprockets
-
How to Access Hash Values Like Methods in Ruby
Propshaft is an asset pipeline library for Rails. It uses OrderedOptions to define the config.assets settings, instead of creating a new configuration object. You can read the complete source on Github.
-
How to migrate rails sprockets to propshaft
Propshaft has a smaller scope than sprockets and requires you to rely on the js-bundling and css-bundling gems to handle the building of CSS and JS assets. Read the docs for an extensive upgrade guide.
-
New view helpers for jsbundling ?
[They have a replacement in the works for sprockets](https://github.com/rails/propshaft), but I'm ignoring it for now. Just coping with js-bundling and css budling is enough for me.
-
February Gnarly Learnings #1: An Introduction to Propshaft
What an exciting couple of months it has been for the Rails community! Rails 7 was released in December of 2021 and this month we are welcoming Propshaft. David Heinemeier Hansson (DHH), the creator of Rails, released a post on Feb. 11 introducing the community to the new and improved asset pipeline for Rails. While Propshaft likely won't be the default until at least Rails 8, it promises a simpler solution to asset management over its predecessor, Sprockets. Sprockets, the current default asset pipeline library, has grown increasingly heavy over the years as it has attempted to shoulder all things related to bundling, minifying, transpiling, and compressing. Enabled by the new era of tech that makes Rails 7 possible, Propshaft is touted as being "absolutely tiny" in comparison and aims to provide the following: a configurable load path for your assets, digest stamping for long-expiry cache and better performance, a development server that removes the need to pre-compile assets, and basic compilers instead of full transpilers. Sprockets will require relatively long-term support and will remain the default for now but fret not! You can create a Rails 7+ app using Propshaft, or upgrade an existing app and start using it now.
-
HEY is now running with Propshaft + Dart Sass; no more Sprockets, sass, sassc…
There’s more info on the GitHub repository, stating
-
Rails 7, import JavaScript from Engine
Oh and there's a new option https://github.com/rails/propshaft which will replace sprockets in the future, didn't use it though, but looks promising
What are some alternatives?
importmap-rails - Use ESM with importmap to manage modern JavaScript in Rails without transpiling or bundling.
cssbundling-rails - Bundle and process CSS in Rails with Tailwind, PostCSS, and Sass via Node.js.
vite_ruby - ⚡️ Vite.js in Ruby, bringing joy to your JavaScript experience
sprockets - Rack-based asset packaging system
hotwire-rails - Use Hotwire in your Ruby on Rails app
dartsass-rails - Integrate Dart Sass with the asset pipeline in Rails
esbuild-live-reload
Ruby on Rails - Ruby on Rails
Webpacker - Use Webpack to manage app-like JavaScript modules in Rails
spree_backend - Spree Admin Dashboard
esbuild - An extremely fast bundler for the web
factory_bot - A library for setting up Ruby objects as test data.