I wrote a roadmap-style post about why the developer experience for Nuxt developers should get much faster over time. It covers Vite 8/Rolldown, Oxc (oxlint and oxfmt), TypeScript 7, the pnpm Rust engine, Nitro v3, and possible future improvements like Vite’s full bundle mode and Vize.

The post connects work happening across VoidZero, NuxtLabs, and the wider Vue/Nuxt ecosystem, and explains what is usable now, what is coming soon, and what is still experimental - so you can better understand what may affect yourr projects and which tools are worth watching.

It is my first blog post, so feedback, or other thoughts from the community would be very welcome.

https://norbiros.dev/blog/nuxt-dx-is-getting-faster

I'm currently building a Canada based EV platform with fancy words like "Prairie" and "Québec" (remember the "é") and for the life of me, couldn't figure out why my browser kept screaming about "hydration mismatch"

It turns out Chrome saw "Québec" and said "fck yea, let's translate"

It not only translated it to replace the "é" with a regular "e" but also translated "prairie" to "meadow" 😅

My French is passable, but I was so frustrated, and had pulled my last hair out to even guess that's what was causing the issue, even after I started seeing random "meadows" on the pages.

The client has plans to have it in both languages (🇬🇧/🇫🇷), but for now the quickest fix was a:

// nuxt.config.ts
app: {
  head: {
    meta: [{ name: "google", content: "notranslate" }]
  }
}

Boring post, but I hope it helps someone, especially if you're working with content in different languages

Hey guys. Have a very big project (15+ nuxt layers) that is kinda insane to build - dev server is very slow, build takes around 15gb of RAM, and there's no ETA on nuxt 5 to adopt rolldown. also tests are slow because of nuxt/test-utils, which bring a lot of harness.

application is SPA, so im thinking of migrating it on clean vite + nitro (v3). i want to make tests faster (since no nuxt/test-utils) and optimize my build and dev server

is there any caveats i should be looking out for?

Wanted to show some appreciation to the people working on Nuxt. It has been very useful for us, so here's a quick rundown of how we use it.

The site is the usual SaaS mix: marketing pages, blog, docs, pricing, plus public share pages where users can publish an interactive mindmap at /m/:slug. Our first instinct was static site + separate viewer app, but route rules let us keep it all in one Nuxt app:

Everything content-shaped (homepage, blog, docs, legal) gets prerendered through Nitro. Pricing is SWR with a 5 minute TTL and reads the plan catalog from our backend through a Nitro server route, so I never have to update pricing copy in the website repo when plans change. The share pages use the same SWR boundary: the server renders OG tags, canonical URL and a plain HTML outline of the mindmap for crawlers, then a <ClientOnly> canvas takes over in the browser.

One issue we hit, and the workaround: crawlLinks: true does not discover pages behind a redirect. /docs is a redirect-only route, and the crawler wouldn't follow it into the nested docs pages, so we ended up listing all ~30 docs routes explicitly in nitro.prerender.routes. If anyone has a cleaner alternative, let me know.

Rest of the stack -> Nuxt Content with typed collections for blog and docs, sitemap with zeroRuntime so the sitemap is a build artifact, Shiki dual-theme highlighting, Tailwind via PostCSS.

Site: https://agentbayes.com
Sample public share: https://agentbayes.com/m/jQS6rZ

I wanted a library like vis.js but needed it canvas-based for server-side rendering without a headless browser in node, so I built one. I'd love to get some feedback.

After the recent PrimeVue announcement, I've seen quite a few discussions from developers exploring alternatives.

I'm a contributor working closely with the Vuetify ecosystem, and I'm exploring an open-source project to reduce the migration effort from PrimeVue to Vuetify.

The current idea includes:

• Aura-inspired theme (WIP - Img-1)
• PrimeVue component aliases (Img-2)
• Props mapping (PrimeVue ↔ Vuetify)
• Migration guide

The goal is not full compatibility.

The goal is reducing migration friction.

I'm trying to validate whether this solves a real problem before investing a lot of time into it.

If you're considering moving away from PrimeVue:

• What's your biggest blocker?
• Which components would you need first?
• Would something like this actually help?

I'd really appreciate honest feedback.

https://preview.redd.it/ksodszx1vfah1.png?width=2424&format=png&auto=webp&s=a2c4f0ac906391fccdcbd2b7ab91d1ccd0258159

https://preview.redd.it/oa32oyx1vfah1.jpg?width=2140&format=pjpg&auto=webp&s=2fefeb3e9be59bb3aae4c58b44d0631c062a5b17

Hi everyone!

I'm implementing a global HTTP error handler in my Nuxt 4 application and I'd like to properly handle HTTP 429 (Too Many Requests).

I understand what the status code means, but I'm not sure about the best way to implement it in practice.

Do you apply rate limiting only on authentication endpoints (login, register, forgot password), or on the entire API?

Do you return a Retry-After header?

How do you handle this on the frontend? Do you simply show a toast, disable the action temporarily, or implement an automatic retry?

I'd love to hear how you approach this in production applications.

I would like to see your setup.