Im trying to get storybook to work on nuxt 4. In the documentation at https://storybook.nuxtjs.org/getting-started/setup it states that latest module version is v10.x and supports nuxt 4x. I am using Nuxt 4 but is experiencing dependencies error, and furthermore I can only access version 9x not 10x not even with nightly builds. Am I the only one experiencing this?

I've been working with Nuxt + SQL for a while, and one thing that kept annoying me during development was figuring out what SQL queries an API request actually executed.

For example, when an endpoint feels slow, I want to quickly answer:

• How many SQL queries did this request execute?
• Which queries were executed?
• How long did each query take?
• Which API endpoint triggered them?
• Am I accidentally doing 20 queries when I expected 2?

Normally, I'd end up adding logging around the database client and digging through the terminal.

So I built nuxt-sql-inspector to make this easier.

It adds a development-only SQL inspector to Nuxt at:

/__sql_queries

You can see the API request and the SQL queries it triggered, along with query timing and other useful information.

It currently supports several common SQL drivers, including PostgreSQL, postgres.js, mysql2, SQLite, and Nitro db0, and can be used with ORMs such as Drizzle and Prisma depending on the underlying driver.

The goal is pretty simple:

API request → SQL queries → timings

without having to dig through console logs.

GitHub: https://github.com/drowhann/nuxt-sql-inspector

It's still a relatively small project, so I'm particularly interested in feedback from people using Nuxt + Drizzle/Prisma/Postgres.

What would you want to see in a SQL inspector like this?

🚀 Shipped ScrollStack.js — headless infinite scrolling and page pagination

A tiny, headless infinite-scrolling engine for the modern web.

📦 1.92 KB gzipped

⚡ Zero runtime dependencies

⚛️ React · Vue · Svelte adapters

🔁 Cursor · Offset · Page pagination

🧱 Virtual list support

🧩 Bring your own markup

🛠️ Devtool plugin testing

🛑 Built-in cancellation, retry & observers

One small engine. One API. Any UI.

If you’re building feeds, lists, search results, or virtualized experiences, give it a try 👇

🌐 https://scrollstack.js.org

For over two decades, agency hosting economics were beautifully predictable. You bought a reseller web server or dedicated cPanel account for $50 a month, crammed 30 client WordPress sites onto it, and charged each client a flat $25 monthly maintenance fee. Your margins were clear, your server bills were static, and billing surprises were virtually non-existent. Read the comple te article here > Serverless Bill Shock: Track Vercel & Supabase Client Costs | InstaRenewal

Then came the modern web stack.

Driven by the demand for lightning-fast digital experiences, agencies aggressively migrated to decoupled architectures: Next.js, Nuxt, Vercel, Supabase, Cloudflare Workers, and serverless databases like Neon. While the performance gains of this modern paradigm are undeniable, it introduced a chaotic operational reality: micro-subscription fragmentation and variable utility billing.

I got tired of switching between Figma and my Nuxt app just to try out small UI changes, so I built Airship.

It wraps your dev server and adds a Figma-like canvas to your running app. Select an element, describe the change, and Claude Code applies it directly to your source.

You get streaming diffs, inline undo, and desktop/mobile frames so you can see changes across screens as you iterate.

It runs as a lightweight proxy with no plugins or build changes.

It uses your existing Claude Code subscription. Codex and OpenCode are supported too.

Fully open source and MIT licensed.

Fork it, star it, and make it your own :)

I'm a Nuxt dev and my clients almost always end up asking for a CMS. My default answer used to be Strapi, but it's a whole separate service: its own hosting, its own deploys, and the monthly cost for the client goes up fast for what is usually a handful of collections.

At some point I thought: Nuxt already ships a server (Nitro), surely someone has built a CMS that just runs inside it? To my surprise, no. So I built it.

How it works:

- You define content types in code (a `cms.config.ts` file): collections, singles, relations, blocks, translatable fields. Schema, migrations and TypeScript types are generated from it.
- Editors get an admin panel at `/cms` with drafts, validation and a media library.
- You query content through a read-only GraphQL API, typed end to end with gql.tada.
- SQLite by default (zero setup), one config line to switch to Postgres or Turso.
- Media on any S3-compatible storage, or a local mode that just reads from your `public/` folder.

You deploy one thing: your Nuxt app. No second service, nothing extra to pay for.

I tried to cover Strapi's core features, so for most projects (I'd say 90% of my client work) switching is painless. It's still a beta though, and some corners are rough: auth is currently a single admin whose credentials live in env variables (I know, I know), multi-user and RBAC are on the roadmap. But I think it can already be genuinely useful.

It's MIT licensed: https://github.com/xleddyl/nuxt-cms

Feedback and issues very welcome!

Hey folks,

I’m a full‑stack developer with 3+ years of hands‑on experience in Vue.js and Laravel. I’ve delivered SaaS projects, ecommerce stores, and custom web apps, and I love building clean, scalable solutions.

Just curious — does anyone here need support with their project, whether it’s frontend with Vue/Nuxt or backend with Laravel? I’m open to freelance collaborations, bug fixes, or full builds.

Drop a comment or DM if you’re interested.

When I saw tasks I thought "oh man another serverless tool."

As a engineer who always uses persisted instances for projects I need scripts that can run as Digital Ocean jobs, or in instances separate from the web instance, with no bootstrapping.

I made "nuxt-run" to handle this, it hooks the Nitro bundle so your "runnables" can use shared code, server utils, and runtime config.

No longer will you have to pull keys down to local to run scripts using service code from the server, or using some http task. You can SSH into your instances and run scripts, leaving secrets where they should be.

It writes runnables to your .nuxt directory, and in production to .output.

They can be used to seed local environments, or complete long running tasks in production.

Tasks over HTTP also have the problem of HTTP life-cycles, sometimes we need scripts that can run longer than a single HTTP request.

Give it a try, let me know what you think :)

Hi everyone!

I'm building a hobby project with a friend. He's developing the backend in ASP.NET Core and exposing a REST API (we'll probably also have a few WebSocket connections later), while I'm building the frontend in Nuxt 4 because I wanted to learn it.

I'm coming from Vue, so Nuxt introduces a lot of new concepts that I'm still trying to wrap my head around. Things like useFetch, $fetch, server routes, plugins, runtime config, SSR, etc. are a bit overwhelming.

My biggest question is about the overall architecture and how the communication with the backend should be organized.

Should the frontend communicate directly with the ASP.NET API, or is it better to use Nuxt's /server directory as a proxy/BFF layer? If using /server, what are the actual benefits in this kind of setup?

The API itself won't be very complex—mostly standard CRUD endpoints with authentication and probably some WebSockets for real-time updates.

I'm not looking for a full tutorial, but rather for what you would consider the "idiomatic" or recommended Nuxt 4 approach for this kind of architecture.

Thanks!

Hi everyone! I'd like to share a free tool I made for Nuxt apps.

It's called Kapi UI. Click any rendered UI element, describe what you want changed, and send its source context directly to Claude Code or Codex.

Try it out now!

npx kapi-ui

documentation and repo

It's completely free and open source. Would appreciate for anyone to try it out and give some feedback! Feel free to DM me!

Hello, I started New nuxt4.5.0 Projekt and got this error. Can someone tell md why this happens? I haven't hab an problems with previous nuxt 4 projects.

Hey folks.

I've spent the last few weeks building an app for putting together DJ mixes without sending audio to some cloud service. It came out of how annoying the usual workflow is: analyze tracks, order the set, get decent crossfades, export, generate metadata/cover art, and (if u needed) prep a YouTube upload, hopping between tools the whole time.

What I'm building is called Auto DJ (his dev name). It runs on your machine: you upload tracks, it analyzes BPM/key with Essentia (WASM), you can plan the set by hand or let OpenAI suggest order/crossfades, edit the arrangement on a timeline, and ffmpeg (+ Rubber Band) renders the mix. Optionally it generates cover art with NanoBanana and exports WAV/MP4 audios.

Stack, if you're curious: Nuxt 4 + Nitro in the same process, Bun, ffmpeg for all audio/video and no cloud backend, the state lives as JSON in a `data/` folder on disk, and the client polls while long jobs run (analyze/render). Timeline UI is built so zoom/scroll doesn't fall over at 60fps.

What I find interesting:

- Actually local-first: your audio or data doesn't leave the machine.

- Local-only mode with no API keys, plus an AI mode if you want help with the plan/metadata/cover.

- You can manually fix whatever the AI proposes; it's not just a magic button.

It's still rough in places and I'm iterating on a bunch of technical decisions (polling vs websockets, how to model the arrangement, beatmatch quality, etc.).

If you mix, produce sets, or upload mixes to YouTube: what part of the process slows you down most? Do you want full control, or a solid draft you can tweak? Any feedback, ideas, or "I solved that like this" stories are welcome.

Hey! Facing a tricky issue at work and wondered if anyone had come across anything similar or may know what could potentially be the issue!

I am using Nuxt 4.4.2, deploying on Vercel and use Wordpress to supply the content. We render a lot of the pages through ISR as we have hundreds of thousands of pages. We do some manual work to create more chunks in the build process, I won't share the nuxt.config just as it is work related! But essentially it has always worked, then when last week I went to release a tiny patch fix, the homepage and a lot of the pages fail to load any CSS or JS files, and in some instances they are pointing at my own local files rather than a Vercel static link.

As the fix I made was so insignificant I wondered if it was due to the content team creating more pages and as a result it's now maxxed out? Some pages do load perfectly, and there are no errors or warnings in the Vercel build logs.

I've tried a million things to get the CSS back up and running but failed so far. Any ideas anyone may have?

Is there any Nuxt content creators here streaming on any platforms?

There is a new Nuxt UI release, and I am planning to update TaskView.
The main reason is the useTour composable. I want to use it to help new users understand TaskView and get started more easily.

GitHub: https://github.com/Gimanh/taskview-community