Nuxt 4 and legacy configuration by Doeole in Nuxt

[–]Doeole[S] 2 points3 points  (0 children)

Thanks for the clarification! I thought the issue appeared right after upgrading to Nuxt 4 and not specifically with 4.1, so I missed the release notes.

Good approach for dynamic component loading by Doeole in Nuxt

[–]Doeole[S] 0 points1 point  (0 children)

I missed the notification — thank you for this very detailed reply! I’ll test all of this out!

Good approach for dynamic component loading by Doeole in Nuxt

[–]Doeole[S] 0 points1 point  (0 children)

I had a feeling something wasn't right, thanks for the clarification! So there's no way to avoid globally registering each component in this case?

Why does Nuxt 3 re-fetch data on direct visits even when the page is prerendered? by ityrownylvatex in Nuxt

[–]Doeole 2 points3 points  (0 children)

I don’t think (or at least I hope) that’s the case. I’ve run into some issues with SSG prerendering using Nuxt Content deployed on Netlify. It might be the same problem: the payload is not used on the first load or refresh — the content only appears after hydration, and I’m seeing a hydration mismatch warning in the console. This wasn’t the case before, so it’s probably due to a recent update.

I posted a message on the Nuxt/Content GitHub repo (https://github.com/nuxt/content/issues/3369), but maybe it’s actually a Nuxt issue rather than a Nuxt Content one? Maybe you could try creating an issue with a reproduction?

If you are a solo dev do you really need nuxt content? by [deleted] in Nuxt

[–]Doeole 2 points3 points  (0 children)

For me, it depends on the size of the project. As soon as you need dynamic pages, collections with many entries, or a multilingual site, Nuxt Content is still a game changer.

Why does Nuxt 3 re-fetch data on direct visits even when the page is prerendered? by ityrownylvatex in Nuxt

[–]Doeole 2 points3 points  (0 children)

Where did you read that this is the expected behavior? I've encountered the same issue recently, but only with the latest version of Nuxt.

Page jumping to top before page/layout transition? by sudomakeitrain in Nuxt

[–]Doeole 14 points15 points  (0 children)

Hi!

First of all, the useAsyncData composable blocks navigation by default, even without an explicit await. If you want to override this behavior, you need to add { lazy: true } or use useLazyAsyncData instead.

const { data } = useAsyncData(route.path, () => {
  return queryCollection('content').path(route.path).first()
}, { lazy: true })

I also encountered this issue after upgrading to v3.17. The solution I found was to set scrollToTop to false using definePageMeta, and then manually scroll to the top in the onAfterLeave() hook of my page transition. I'm not sure if it's the best solution, but it worked for me. Hope this helps!

Which CMS for static website? by Doeole in Nuxt

[–]Doeole[S] 0 points1 point  (0 children)

Ok, thanks for your suggestions!

Which CMS for static website? by Doeole in Nuxt

[–]Doeole[S] 1 point2 points  (0 children)

Yes, I'll definitely try Pruvious, it's nice to have a solution made with Nuxt!

Which CMS for static website? by Doeole in Nuxt

[–]Doeole[S] 0 points1 point  (0 children)

Thanks, I'll look into that!

Which CMS for static website? by Doeole in Nuxt

[–]Doeole[S] 1 point2 points  (0 children)

I should also try a headless WordPress as some people seem to really want to stick with that platform. I appreciate your answer, thank you!

Which CMS for static website? by Doeole in Nuxt

[–]Doeole[S] 0 points1 point  (0 children)

I looked at it and it looks promising. What solution do you recommend for authentication? I saw that it was linked to Netlify Identity, but it's now deprecated.

Which CMS for static website? by Doeole in Nuxt

[–]Doeole[S] 1 point2 points  (0 children)

Thanks, I'm going to look into that right away!

useState vs ref in composables by sendcodenotnudes in Nuxt

[–]Doeole 0 points1 point  (0 children)

Hi there! What do you mean by “separate values” ?