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.
Anshuman Bhardwaj Hi @hasriza, welcome to the Vercel Community! Thanks for taking the time to write up detailed feedback. I'll share it with the team. As with any AI product the output should always be double checked because the AI editors are prone to overdoing or hallucinations.
riza Hi @anshumanb, I do agree with your point regarding hallucinations and as valid as it is, if there was a way to list and restore deleted files and folders after the new version is created, it would probably save a lot of time in my opinion. I also have a feeling that these files are not explicitly deleted but are lost mid generation due to incomplete implementation of the changes requested.
Richardnugen 6495 This also happens in my environment. Especially with any changes I make outside of v0. For instance, if I pull the code locally from github, modify, push and then sync in v0. The next edit v0 will delete my changes. It is very aggressive with this. For instance, I changed the .gitignore file and it delete my changes. Not to mention the forms I created and routes I added.
Marlon Vidal having the same problem here
Jacob Paris You can clear the chat history at any time by clicking "Fork". This will create a fresh chat in the same project with your deployment settings, environment variables, integrations, etc all intact, and if you deploy the new fork it'll take over as the main deployment for that generation I rarely get beyond v20 before forking to a new chat and usually fork every time I deploy
Anthony Yang Thanks for getting back to me, Jacob — much appreciated. I’ll give the “Fork” method a try, as it sounds like a logical way to maintain performance while preserving the project setup. I’ll return to the thread once I’ve tested it to share whether it resolves the slowdown. Thanks again.
Bernd Strehl I had a similar problem. I'd recommend to create a new Next.js project with tailwind and copy over the code without the configs, then it should be consistent.
Pauline P. Narvas +1 Thanks for jumping in here! @bardiamardan Any luck?
Bardiamardan Well my project is super messed up because of this, I mean when you move your files with mismatched css, the whole globals.css messes up and I just can't merge them correctly (half of the styles are in styles/globals.css, half of them are in app/globals.css and again half of them are in tailwind config) I just don't know what to do
Pauline P. Narvas Happy to help here, Sebastian! Could you make sure the chat link is unlisted so that we can view it?
Sebastian I have done the change
Pauline P. Narvas From what I can see, it looks like you have a couple of errors in the chat. Maybe that is what is preventing you from deploying. Can you fix those first then try again?
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
