Maximo Mussini

@kennnG Yeah, using it in production every day.

@MaximoMussini Just discovered this, amazing work. Are you still maintaining it?

Announcing oj_serializers v2.0 ⚡️ 🚀 Improved performance (20% to 40% faster) 🤩 Simplified API, easier to use 🛠 More configurable (transform keys, sort attributes) ✅ Backwards compatible github.com/ElMassimo/oj_s…

I created a Vite.js plugin: github.com/ermolaev/vite-… for faster HTML reloading in the browser using Hotwire Turbo (for Rails apps and beyond) instead of a full page refresh. It also supports HMR for Tailwind CSS. Inspired by (forked from) @MaximoMussini vite-plugin-full-reload.

@RogersKonnor @palkan_tula Thanks for the kind words, Konnor 😊

Why I think Vite (Ruby) is the only viable option (among available today) for Rails apps? It the only one that is capable* of surviving major framework upgrades, DHH mood swings and uncontrolled frontend tooling evolution. Vite is kinda meta builder: it relies on esbuild and rollup for dirty work. Whenever a new shiny frontend builder appears and overcomes esbuild (which is a great builder, for sure), Vite would switch under the hood without enforcing you to migrate yourself. Using Vite Rails instead of sprockets|propshaft+importmap|jsbundling|cssbundling|tailwindcss-rails|esbuild|bun (pick your own combination) allows you to stay independent of Rails frontend “evolution”. More major versions covered, less painful upgrades. I switched to Vite ~3 years ago and forgot about asset pipeline stack upgrades. It works today in a similar fashion it worked back then.

JS frameworks are just the better tradeoff for long-session productivity apps. Much higher upper-limit for the UX. And the DX is not as complicated as some anti-JS folks claim to be - reminder that there are easy ways to integrate Vite in Rails: vite-ruby.netlify.app/guide/rails.ht…

@owaiswiz @joeldrapper Thanks for sharing, that's what I use with Phlex: // vite.config.ts import reloadOnChange from 'vite-plugin-full-reload' export default defineConfig({ plugins: [ reloadOnChange([ 'app/views/components/**/*', ]), ] })

@joeldrapper (its from the author of vite_ruby)

@antfu7 Agree 💯 It has a lot of benefits and can't think of any downsides. maximomussini.com/posts/trailing…

I can't think of any reasons you don't enforce dangling. I'm genuinely very curious about why.

If you are not using comma dangling - why? 🤔

@manufaktor Nice! @inertiajs is great for this kind of integration, and has the advantage of not requiring Vue Router. Check github.com/ElMassimo/ping… for an example (a bit outdated).

Not sure if you can see from the video, as twitter butchered it. But basically after rendering the Vue template, the client side router takes over.

Started integrating @vuejs into the beautiful @rails conventions, effectively making Vue what it should to be, per its name: the view layer Powered by @vite_js and vite-ruby from @MaximoMussini

Upgraded types_from_serializers to support oj_serializers v.2.0 ✨ 🤖 Automatically generate TypeScript ✅ Minimize bugs in the frontend 🕶 Infer native types from your SQL schema 🚀 Generated instantly on file changes #ruby #rails github.com/ElMassimo/type…

@palkan_tula Would love to support Hanami 2 out of the box! Haven't received any related comments in the repo; it's likely that folks using @hanamirb are not using Vite. Should be easy to adjust the installer, @jodosha let me know if you are interested. vite-ruby.netlify.app/guide/hanami.h…

Then, I needed a way to add CSS (Tailwind) and JS to the app. For that, I decided to use Vite Ruby by @MaximoMussini. The existing vite-hanami plugin was built for Hanami v1.3 and is incompatible with v2.0. Though, it helped me to build a PoC: github.com/anycable/anyca…

When we with @kalashnikovisme started working on this post, we planned to release it as a case study: less code, more product, Rails, Hotwire, bla-bla. But then, we decided to make a twist and go off Rails and Google APIs—the challenge full of the joy of problem-solving...

⚡️ Join @MaximoMussini to learn how @vite_js can improve your development workflow, how to use it in Ruby web applications, and how it compares to other tools that are available in @rails! ❤️ youtu.be/SpeKA9fA6gg

💎✨New Release✨💎 Happy to announce that Vite Ruby will now install @vitejs 4 by default. You can upgrade your #ruby and #rails projects by running: ⌨️ bin/vite upgrade

✨ New Release ✨ 🏝 @ilesjs 0.9 now runs in @vite_js 4

@Eo9394u4vshdhne Hi Kacper! I'm using it with active record. See: #sql-attributes" target="_blank" rel="nofollow noopener">github.com/ElMassimo/type…

@MaximoMussini I was wondering, is your gem types_from_serializers configurable with ActiveRecord?

@JLarky @ilesjs @nickemccurdy @reactjs @preactjs Gotcha, that's not the typical "island", so in that case the additional bundle size is probably a non-issue 👍

@MaximoMussini @ilesjs @nickemccurdy @reactjs @preactjs in what way it's not ideal? If my landing page is static and only after I navigate to /dashboard I download my react app? :) also, we had 7 years to understand that preact/compat is not the answer, otherwise, everyone would have used it already ¯\_(ツ)_/¯

Things are going pretty bad. It looks like if I start using next it will actually improve the performance :) trying out vite next :) Before next I did all the cool things like remix, astro, qwik and solid, but not having HMR is a deal breaker

@ilesjs @JLarky @nickemccurdy @reactjs @preactjs Using a framework with a large bundle size is not ideal if your goal is to do partial hydration, but you do you 😄 As a reminder, preact/compat is great, and you can configure Vite so that you can keep typing `from 'react'`.

@JLarky @nickemccurdy If you'd like to use @reactjs in @ilesjs, a pull request for an adapter is welcome! Shouldn't be too different from the @preactjs bindings: #L17-L26" target="_blank" rel="nofollow noopener">github.com/ElMassimo/iles… github.com/ElMassimo/iles…

Join me on the Discord channel to ask questions or chat about it: discord.com/channels/80401…

My talk: Frontend Joy in Ruby on Rails at @ViteConf is about to start! Come watch! viteconf.org/live?talk=fron…

So excited to be a part of ViteConf this year! 😃 If you've heard of @vite_js but haven't gotten around to trying it yet, this talk has got you covered! #vite #ruby #rails