Should I use next 13 or t3 stack for my current project (long term project)
if i do use t3, how difficult would it be to update to next 13 when it does become stable. also worried about how to use tRPC. i also def need the nested routing
7 Replies
For now I would go with t3 and Next 12 and start the upgrade after some time (like 2 - 3 months) at least that's what I am going to do with my current app which btw would benefit a lot from the new Next 13 release.
I don't think migrating over to Next 13 is going to be a difficult process, just time consuming (they said that pages and apps directories can run simultaneously)
Unknown User•3y ago
Message Not Public
Sign In & Join Server To View
also worried about how to use tRPCi'm going crazy with that part lol. I can make it work on dev or build locally but it will fail on vercel (same with RQ). And I can't find anyone even mentioning about it so idk if i'm doing something astronomically stupid or if its an actual issue :(
i think rq just doesn't work in next 13
works locally tho
okay I just tested with plain useEffect() fetching, it still has the same error
seems like something to do with calling /api end points?If you need to start it now, use T3
Might mean a bit of work down the line migrating to the new stuff, but you can start now instead of whenever the new stuff is ready
update: i got it to work on vercel, after a painful debugging session in sub channel