Using Hotwire Turbo in Rails with legacy JavaScript

1

Yarn

Rails 5.1 optionally adopted the webpack bundler and the yarn package manager (2017), the two became the preferred way of handling JavaScript in Rails,.

#Front End Package Manager #Package Manager #JS Build Tools 109 social mentions

2

Webpack

Rails 5.1 optionally adopted the webpack bundler and the yarn package manager (2017), the two became the preferred way of handling JavaScript in Rails,.

#Web Application Bundler #JS Build Tools #Module Bundler 220 social mentions

3

HEY

The new Basecamp’s flagship – the HEY.com service – currently uses a total of ~60kB of JavaScript (zipped) while, in terms of reactivity, it feels like a real SPA. In contrast, our web uses twice as much JavaScript while mostly being an ordinary click-and-wait-for-the-whole-page web, oh well….

#Email #Email Clients #Communication 21 social mentions

4

Turbolinks

Since Rails 4, the Turbolinks library has been included but had a bunch of problems at that time (2013), so.

#Code Collaboration #Javascript UI Libraries #Web Application Bundler 13 social mentions

5

Webpacker

Rails 5.1 optionally adopted the webpack bundler and the yarn package manager (2017), the two became the preferred way of handling JavaScript in Rails,.

#Web Application Bundler #JS Build Tools #Esports 15 social mentions