⌘K
David Moreno Thanks for sharing, Christian! This looks super helpful — I appreciate your work on making i18n management easier in Next.js projects. 🙌
Christian Ivicevic Thanks for the kind words - let me know if you were able to give it a try and whether everything works as expected. After all, it's quite the difference running this "just" for my own side projects and having others attempt to integrate it into their own workflows.
Pauline P. Narvas Hey, @kamalabdulmumin0-gma! Welcome to the Vercel Community 👋 If I'm understanding correctly, you'd want to set up something like what is detailed in this guide: vercel.com/guides/how-can-i-serve-multiple-projects-under-a-single-domain Let us know how you get on!
Pauline P. Narvas Hey @kamalabdulmumin0-gma, just checking in to see if you still need help with integrating your three projects or if you've made any progress. Let us know if you have any questions or need further assistance!
Anshuman Bhardwaj Hi @fulwing, welcome to the Vercel Community! Thanks for sharing your issue in such detail. However, it'd be great if you could please share your public repo or a minimal reproducible example. That will let us all work together from the same code to figure out what’s going wrong.
system Hi @fulwing! 🙂 We haven't heard back from you. If you're still stuck, feel free to share any updates, logs, or additional context that might help us assist you better!
Anshuman Bhardwaj Hi @hammad-shaikh, welcome to the Vercel community. Thanks for posting your question here. I've fixed the issue with your account with the help of our support team. You should be good now. If you need any other help, you can always post it on the community.
Neerajkumar61 @ Hammadshykh Thank you for reaching out to Vercel; community. You should be good to go.
system Hey @hammad-shaikh! 👋 Just wanted to follow up here. If you've found a solution or still need help, let us know! We're happy to continue assisting.
Pauline P. Narvas Hi, and welcome @okiemutegold! The slow rendering issues you're experiencing, even with static pages, could be due to several factors in Next.js 14.1.0. The inconsistency between pages suggests it might be related to how your application is handling server-side rendering (SSR) and hydration. Some ideas to address this: Make sure you're using the app directory for improved performance Check for unnecessary data fetching in your layout files that might delay rendering Review your use of NextAuth to optimize session handling, as authentication checks can introduce overhead. For debugging, add per
Okiemute Gold Hi @pawlean, Thank you for the links, I have checked before, but will again with these. For the points: I'm using app directory I'm not performing data fetch in any of my layout file I fetch data in page, but the page still delays (I doubt server action is responsible, please any thought?) I'm using suspense where needed Static pages like /privacy should load on the fly (you mentioned several factors, can you please elaborate?) checking a session before redirecting user or continuing on route should not cause this lag in layout or other components (any thoughts?) Thanks
Okiemute Gold Hello @pawlean, It was an issue with cookie bot script and facebook script I used in my layout.tsx. Do you know how best this can be done and not have it interfere with page navigations / routing. I'm already using Script tag in the head cookie: <Script id="Cookiebot" src="..." data-cbid="..." data-blockingmode="auto" type="text/javascript" strategy="lazyOnload" async /> fb: <Script id="fb-pixel" strategy="afterInteractive" dangerouslySetInnerHTML={{ html: ... }} /> <noscript> <img height="1" width="1" style={{ display: "none" }} src={facebook.com/tr?id=${process.env.FB_ID}&ev=PageView&noscrip
