4 ms·
> Recently, upgrading from v3 to v4 in a Next.JS project, which was supposed to be a no brainer, turned out to be a four hour ordeal. You might think that is t
by arvinsim 2y ago
> Recently, upgrading from v3 to v4 in a Next.JS project, which was supposed to be a no brainer, turned out to be a four hour ordeal.
You might think that is too long but that amount of time to migrate IMO is short.
What I am dealing now is a mix of styled components, SCSS and global styles. 4 hours is not even close enough to deal with half of it.
I will take TailwindCSS any day over this mess.
- code_for_monkey 2y agoi think theres a divide between people who have worked in good front end repos and ones whove worked in horrible ones. I had to work on an app that was a mix of styled components, scss, inline styling, and globals. It was a wreck and every change took longer because of all the spaghetti styling you had to eat, Id take tailwind in a heartbeat over that.