Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup

nauman.medium.com

Post reply on HN
Print view View original

91–100 of 101 posts

Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup

#91

Post by andrew_ »

tqkxzugoaupvwqr wrote: post #83
AprilArcus wrote: post #74

Earlier quoted context omitted.

I sincerely do not understand this complaint. Do you dislike bug fixes and new features? Would you be happier with a stagnant tooling ecosystem?

Sadly it’s the constant barrage of breaking changes. It’s not just a version number bump and everything keeps running. Patch version breaks the app. Minor version breaks the app. Major version breaks the app (understandable in semver) but multiple inter-dependencies need to be updated in parallel.

I maintain oodles of npm packages, several of which enjoy over 5 million weekly downloads. They have dependencies, and I cannot support your claims.

Sure - some packages in the ecosystem will not follow semver, some will let breaking changes sneak in where they aren't supposed to be. But you'll find this in any pluggable or package manager ecosystem. Please, measure your frustration and choose not to paint with such a wide brush.

Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup

#92

Post by ng12 »

faizshah wrote: post #85
ng12 wrote: post #84

Earlier quoted context omitted.

In curious why you feel the need to do that? I typically only update dependencies either for serious security issues or new features I really, really want to use. I still have a few projects running Webpack 1 without issue.

Large companies often have security mandates that dependencies should be regularly updated.

Well, sure. Dogmatic policies like that will cause all kinds of problems.

Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup

#93

Post by buf »

edoceo wrote: post #24
buf wrote: post #8

Earlier quoted context omitted.

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.

Can you show it?

Closingcredits.com

Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup

#94

Post by nauman »

adamwathan wrote: post #65

Creator of Tailwind here — if you don’t want to go deep into JS tooling and really just care about spitting out a CSS file, it's a lot simpler to just use our CLI tool: https://tailwindcss.com/docs/installation#using-tailwind-cli

Thanks for responding, I wrote this to keep a record of my steps for future reference. I did not intend that this was the only way or the right path

As I've seen many tutorials that were too complex to set up JIT with Tailwind, I thought it might be helpful to others as well who were having difficulty.

The next version of Rails will eliminate webpacker anyway, so I'll write for it

Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup

#95

Post by blacktriangle »

mberning wrote: post #44
toberoni wrote: post #5

It'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.

That has been the most disappointing thing to me with rails. The ruby part of it is so nice. The front end has always made me feel doubtful. It’s not really the rails team fault that the frond end landscape is so tumultuous.

I think a huge part of the problem is that they keep trying to Railsify the front-end. It's impossible to build a decent abstraction over as fractured and fast-moving a target as the whole front-end tool chain. Webpack is already annoying as is, hiding it behind the webpacker gem for no good reason was a shitshow.

Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup

#96

Post by blacktriangle »

tolien wrote: post #15
kayodelycaon wrote: post #11

Earlier quoted context omitted.

The majority of hoops jumped through in the article are entirely of the writer’s own making. They changed the default CSS pipeline and added functionality Rails deliberately does not define. Devise is common for user authentication (and good choice, in my opinion) but it is extremely opinionated and does not like you departing from the blessed path. Rails tends to avoid enforcing patterns beyond the base building blo…

My point about Devise was more “if you’re not using auth, why have you included this?”. I think Rails should probably have a Devise-lite in the box, though. This sounds like the second of my options i.e. gl;hf when the next major Rails release comes around.

Rails choosing not to provide a standard auth solution is 100% the right call. There are a wide variety of auth scenarios, and Devise is highly opinionated. If you're doing a pretty standard B2C type system where you have individual users, Devise fits well, but when you get to more B2B multi tenant with users spanning tenants, and more complicated workflows with users managing other users, Devise breaks down quickly.

Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup

#97

Post by blacktriangle »

paozac wrote: post #6

Useful 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.

What disappoints me is that the Rails team fell for this madness in the first place. Rails in particular has planted its flag on the maximize server-side work camp for the sake of overall tool simplicity. It seems like the Rails team was getting insecure of all the JS hype and "is Rails dying" articles and decided to start chasing trends. I called this the second they shoved webpacker into Rails6 and am not at all surprised this is where we are.

Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup

#98

Post by mberning »

blacktriangle wrote: post #95
mberning wrote: post #44

Earlier quoted context omitted.

That has been the most disappointing thing to me with rails. The ruby part of it is so nice. The front end has always made me feel doubtful. It’s not really the rails team fault that the frond end landscape is so tumultuous.

I think a huge part of the problem is that they keep trying to Railsify the front-end. It's impossible to build a decent abstraction over as fractured and fast-moving a target as the whole front-end tool chain. Webpack is already annoying as is, hiding it behind the webpacker gem for no good reason was a shitshow.

That’s a good point. If it were possible to successfully “railsify” the front end that would be amazing.

Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup

#99

Post by thomasjklemm »

Using Vite with Ruby/Rails is also a modern option [1], really impressed after trying it out.

The article "A Rubyist's Guide to Vite.js"[2] from the author of ViteRuby provides a cool deep dive.

[1]: https://vite-ruby.netlify.app

[2]: https://maximomussini.com/posts/a-rubyist-guide-to-vite-js/

Re: Rails 6 with Webpacker 6, Tailwind 2 with JIT, Postcss 8 and some default setup

#100

Post by bjacobso »

thomasjklemm wrote: post #99

Using Vite with Ruby/Rails is also a modern option [1], really impressed after trying it out. The article "A Rubyist's Guide to Vite.js"[2] from the author of ViteRuby provides a cool deep dive. [1]: https://vite-ruby.netlify.app [2]: https://maximomussini.com/posts/a-rubyist-guide-to-vite-js/

I agree, this feels like the direction the framework should go in the future
Post reply on HN