turbolinks-classic
Classic version of Turbolinks. Now deprecated in favor of Turbolinks 5. (by turbolinks)
Webpacker
Use Webpack to manage app-like JavaScript modules in Rails (by rails)
| turbolinks-classic | Webpacker | |
|---|---|---|
| 2 | 55 | |
| 3,581 | 5,311 | |
| - | 0.0% | |
| 0.0 | 4.1 | |
| over 6 years ago | 23 days ago | |
| CoffeeScript | Ruby | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
turbolinks-classic
Posts with mentions or reviews of turbolinks-classic.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-04-30.
-
Turbolinks and Bootstrap dropdown - why the mess?
Not working with Bootstrap's dropdown menu · Issue #539 · turbolinks/turbolinks-classic (github.com)
-
Using Hotwire Turbo in Rails with legacy JavaScript
Rails 5 came with a major and largely incompatible rewrite of Turbolinks (Turbolinks 5), the previous versions of which were renamed to Turbolinks Classic (2016),
Webpacker
Posts with mentions or reviews of Webpacker.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-28.
-
The Rails asset pipeline, old and new
This is done through the Webpacker::DevServerProxy which is a rack middleware that is added by Webpacker.
-
Asset Pipeline JS Migration
Using Webpacker in Rails provides several advantages over the traditional asset pipeline. First, Webpacker uses JavaScript modules, which allows for better code organization and improved code reusability. Second, it offers modern frontend build tools, such as Babel and PostCSS, for transforming and compiling assets. Third, it provides faster build times and faster runtime performance through code splitting and lazy loading. Fourth, it offers better integration with JavaScript frameworks such as React, Vue, and Angular. Overall, Webpacker offers a more flexible and modern asset management solution for Rails applications. And while Webpacker is being retired, this initiative is to consolidate our code accordingly before moving our bundler to another solution.
-
Thank you Webpacker, Goodbye Webpacker
This article is replace Webpacker with Simpacker and webpack.
- Is enabling full source maps in production a wise default? (2017)
-
How to setup ruby on rails + Angular
in ruby on rails 7 what is the best way to properly install Angular because I can't find any documentation about it. The only tutorial that exists uses webpacker (https://github.com/rails/webpacker) but unfortunately it is no longer supported and no longer up to date in terms of security.
-
What is the pros and cons of using Rails asset pipeline vs. webpack to hold assets?
From the webpacker gem:
-
Webpacker can’t find application.js - fix or bypass completely?
Check this: https://github.com/rails/webpacker/issues/2825
-
Using Rails+ReactJS with Webpacker on VS Code?
instead of using webpacker you should move to esbuild or importmap. Webpacker has been retired a few months ago (cf https://github.com/rails/webpacker) There are videos explained how to set this up (e.g. for importmap https://learnetto.com/tutorials/how-to-use-react-with-rails-7
-
Moving from BS4 to BS5 in Rails 6, having unexpected results
Took me 2 days to find this bug report: https://github.com/rails/webpacker/issues/3188 (thanks again tagliala)
-
Webpacker 6 development continues as shakacode/shakapacker
But it's there in the webpacker README now, if anyone hasn't seen it. https://github.com/rails/webpacker
What are some alternatives?
When comparing turbolinks-classic and Webpacker you can also consider the following projects:
turbo-rails - Use Turbo in your Ruby on Rails app
shakapacker - Use Webpack to manage app-like JavaScript modules in Rails
Turbolinks - Turbolinks makes navigating your web application faster
esbuild - An extremely fast bundler for the web
bootstrap-rubygem - Bootstrap rubygem for Rails / Sprockets / Hanami / etc
Asset Sync - Synchronises Assets between Rails and S3
Stimulus - A modest JavaScript framework for the HTML you already have
Sprockets
turbo - The speed of a single-page web application without having to write any JavaScript
prototype-rails - Add RJS, Prototype, and Scriptaculous helpers to Rails 3.1+ apps
jsbundling-rails - Bundle and transpile JavaScript in Rails with esbuild, rollup.js, or Webpack.
turbolinks-classic vs turbo-rails
Webpacker vs shakapacker
turbolinks-classic vs Turbolinks
Webpacker vs esbuild
turbolinks-classic vs bootstrap-rubygem
Webpacker vs Asset Sync
turbolinks-classic vs Stimulus
Webpacker vs Sprockets
turbolinks-classic vs turbo
Webpacker vs turbo-rails
turbolinks-classic vs prototype-rails
Webpacker vs jsbundling-rails