After almost two weeks of troubleshooting, this is finally resolved:
New nostr:nprofile1qqs2xugc5jyguqkj36rk0syv4tmnkjdtmtperttl7x9rqjy3ustdcvcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg6waehxw309aek2mnyd96zumn0wdnxcctjv5hxxmmd9uxa0uz8 release (finally) coming #soon™!
Note to everyone: try to avoid Next.js at all costs... 😅
Any pointers? We need to upgrade 14 > 15 too
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.
Obviously everyone will hate this comment, but Ruby On Rails is the most battle tested way to make web apps....
If only I was based enough to have learned it before getting into JavaScript hell, lol.
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).
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..
Indeed . Also react and jsx. It’s all trash
