calvadev⚡️
1w ago
After almost two weeks of troubleshooting, this is finally resolved:
New @Shopstr release (finally) coming #soon
Note to everyone: try to avoid Next.js at all costs... 😅
calvadev⚡️
•
2w ago
What started as what I thought would be a simple Next.js update from v14 to v15 ended up becoming a 3 day endeavor to try and fix my entire development environment, ending with me having to revert back to v14 for anything to work... 🙃
See translation
calvadev⚡️
•
2w ago
FUCKING TAILWIND CONFIG GODDAMN IT
See translation
New @Shopstr release (finally) coming #soon
Note to everyone: try to avoid Next.js at all costs... 😅
See translation
7
5
1
1
67
Replies
deeznuts
@deeznuts
♥︎ by author
1w ago
Indeed . Also react and jsx. It’s all trash
See translation
0
1
0
0
0
Rizful.com
@Rizful.com
1w ago
Obviously everyone will hate this comment, but Ruby On Rails is the most battle tested way to make web apps....
See translation
1
0
0
0
0
calvadev⚡️
@calvadev⚡️
1w ago
If only I was based enough to have learned it before getting into JavaScript hell, lol.
See translation
2
0
0
0
0
Rizful.com
@Rizful.com
1w ago
Also, of course, even if you use Ruby On Rails, you still need to do all the JS stuff additionally -- so that's why people sometimes say a Node/Javascript solution is better than a Ruby/Javascript solution..
See translation
0
0
0
0
0
Rizful.com
@Rizful.com
1w ago
Oh, believe me, there is Ruby hell. It can be even darker because not that many people use Ruby anymore. But Ruby On Rails is just SO DAMN MATURE AND STABLE. There are tip & tricks for Ruby on Rails from 2008 that still work perfectly.... And also, Ruby is such a beautiful/readable language (in my opinion).
See translation
0
0
0
0
0
arkinox
@arkinox
1w ago
Any pointers? We need to upgrade 14 > 15 too
See translation
1
0
0
0
0
calvadev⚡️
@calvadev⚡️
1w ago
The middleware, next image optimizations, service worker, and next/tailwind config files are typically what cause a lot of the issues even if error messages are telling you otherwise. If things were working before the migration, it's almost guaranteed that it's not a problem with your code and that the next server configs need to be tweaked in some way.
See translation
0
1
0
0
0