Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup
1–10 of 101 posts
Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup
#2Wait. So… you practically need to develop an app to start developing an app?
When someone tells me to ‘invoke these 3 magic incantations’, I can sort of keep track of it. But here it seems like the instructions are to invoke these 300 magic incantations.
Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup
#3Love seeing the set of gems that folks tend to bring into all their projects. https://github.com/dejan/rails_panel Was a new one for me, will def be checking that out
Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup
#4Wait. So… you practically need to develop an app to start developing an app? When someone tells me to ‘invoke these 3 magic incantations’, I can sort of keep track of it. But here it seems like the instructions are to invoke these 300 magic incantations.
Yeah, one of the key selling points of Rails was that it was Omakase (Japanese: "I'll leave it up to you", i.e. you take the defaults Rails provides) and "batteries included" (i.e. there's enough provided in the box to get a working application).
Having to jump through all these hoops (I'll note that one of the suggested gems is Devise, which provides a framework for user authentication) suggests either this is very much no longer the case or this is tacking on a lot of stuff Rails was never intended to use, which could be fun to maintain down the line.
Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup
#5It's telling that most instructions deal with the Javascript toolchain and not Rails itself. And let's hope that everything works and none of the 2000 imported node_modules blow up when this tutorial is 3 months old.
I'm looking forward to Phoenix 1.6 which ditches Webpack for esbuild. Every step away from the insane churn of the modern frontend world is welcome.
Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup
#6Useful recap. I went through something similar a few weeks ago and the webpack/tailwindcss JIT/postcss setup has been a pain in the ass: dependency hell, outdated documentation, unintelligible error messages.
I'm glad to see that both rails and phoenix guys are looking for a way out of this madness. The writing is on the wall.
Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup
#7It's telling that most instructions deal with the Javascript toolchain and not Rails itself. And let's hope that everything works and none of the 2000 imported node_modules blow up when this tutorial is 3 months old. I'm looking forward to Phoenix 1.6 which ditches Webpack for esbuild. Every step away from the insane churn of the modern frontend world is welcome.
It's still perfectly possible and valid to use Sprockets instead of webpack in a Rails app. That's what i do with every one of my applications and it works flawlesly
Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup
#8It's telling that most instructions deal with the Javascript toolchain and not Rails itself. And let's hope that everything works and none of the 2000 imported node_modules blow up when this tutorial is 3 months old. I'm looking forward to Phoenix 1.6 which ditches Webpack for esbuild. Every step away from the insane churn of the modern frontend world is welcome.
I started a saas company 2 weeks ago with the tool list described in the article. Already at $1k MRR.
IMO, use whatever gets you to paid users fastest.
Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup
#9It's telling that most instructions deal with the Javascript toolchain and not Rails itself. And let's hope that everything works and none of the 2000 imported node_modules blow up when this tutorial is 3 months old. I'm looking forward to Phoenix 1.6 which ditches Webpack for esbuild. Every step away from the insane churn of the modern frontend world is welcome.
It's still perfectly possible and valid to use Sprockets instead of webpack in a Rails app. That's what i do with every one of my applications and it works flawlesly
When I used to use Rails pre-webpacker I felt like I was constantly fighting with sprockets. Trying to use it with assets from node modules isn't always straightforward, and it's pretty slow (or used to be).
Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup
#10It's telling that most instructions deal with the Javascript toolchain and not Rails itself. And let's hope that everything works and none of the 2000 imported node_modules blow up when this tutorial is 3 months old. I'm looking forward to Phoenix 1.6 which ditches Webpack for esbuild. Every step away from the insane churn of the modern frontend world is welcome.
Rails will soon default to using ESM instead of Webpack.
https://world.hey.com/dhh/modern-web-apps-without-javascript...