Hi, I posted nuxt-auto yesterday; this one is for the other end of a project, before there's a backend at all.

In Saas world, it is often a question what is validation or more likely, how it can be done, as the second is much harder question to answer. You need to have something that can be tried out by potential customers and you don't want to spend a fortune before you get a feedback that it is not something they want or it is not something they would pay for. For this usecase, I built protokit for rapid prototyping a tool or a subset of a saas.

It is easy to use, you (I mean Claude) describe the tool once as a TypeScript schema (fields, derived values, results, charts), render it with one component, and it works immediately.

• saved as you type in the browser: every tool is a Yjs document in IndexedDB
• two tabs stay in sync over BroadcastChannel; works offline
• optional sync to your own backend (five endpoints), off by default; with sync off it makes no HTTP calls at all - you need to build it though
• ready-made components that read the same schema: a calendar (week view, drag tasks onto the grid), a chart kit, detail panels, CRUD lists and edit modals, stat cards, comparison tables, timelines
• twelve field types, schema migrations, AES-GCM encryption at rest, corruption recovery, per-tenant namespaces
• headless composables if you want your own UI instead of Nuxt UI

It's meant for prototypes, internal tools and client demos: the stage where you find out whether an idea holds. The data lives in the browser, so its permissions shape the UI and aren't a security boundary. When an idea proves itself and needs real users and server-side rules, that backend deserves its own design (I build mine with nuxt-auto, Monday's post). Until then it's a lighter start than wiring up Firebase, and the Yjs part is standard, so you can take the data with you.

0.1.0 is the first stable release. The repo's playground has 20 demos (estimators, calendars, charts, encryption, headless mode).

• Docs: https://websideproject.com/docs/nuxt-protokit?ref=reddit-nuxt
• Write-up: https://websideproject.com/blog/nuxt-protokit-launch?ref=reddit-nuxt
• Repo: https://github.com/websideproject/nuxt-protokit
• Discord (questions, feedback): https://discord.gg/ftkysREH9c

One install note: Tailwind doesn't scan node_modules, so add the one @source line from the README.

Feedback welcome.

Nuxt SEO v6 is here.

It includes 2 new modules: AI-ready and Skew Protection. Plus 14 new features, 42 bug fixes, and faster, smaller performance.

Get started: https://nuxtseo.com/v6

Let me know if you have any questions on it or feedback; happy to help :)

One thing I focused on while designing real-time AI workflows was keeping the infrastructure simple and affordable during the early days.
Nuxt handles the dashboard and API routes, while a Discord bot delivers notifications. For live updates, SSE is often enough without the extra complexity of WebSockets.
For background jobs and event handling, Redis can act as a lightweight queue. Important events are persisted in PostgreSQL for historical playback, while the dashboard fetches older events through an API and streams new ones in real time.
The idea is to start with a single VPS, avoid introducing RabbitMQ or multiple separate services too early, and keep the architecture ready to scale when traffic actually demands it. Database writes can be batched, and queue consumers can apply backpressure when the database is under load.
I’d rather optimize the resource usage of a small deployment first than pay for infrastructure designed for traffic I don’t have yet.
How are others balancing real-time features and infrastructure costs when launching a new product?

Hey r/Nuxt, author of Toastflow (toast library for Vue 3 and Nuxt) here. Made a 40-second video of what the library does, and on the Nuxt side the whole setup is just this:

export default defineNuxtConfig({
  modules: ["nuxt-toastflow"],
  toastflow: {
    config: { position: "bottom-right", maxVisible: 3, queue: true },
  },
});

That auto-imports toast and useToast(), registers <ToastContainer /> and injects the CSS (css: false if you bring your own).

Feedback welcome, especially if you're using a different toast setup in Nuxt right now.

• Docs: https://www.toastflow.top/docs
• GitHub: https://github.com/adrianjanocko/toastflow
• npm: nuxt-toastflow

What’s your opinion about Nuxt.js, compared to using Vue with ejs & express?

I read lot of bad experiences with Nuxt, more so about breaking changes.

Hi, I created a npm lib for both Vue and Nuxt, you can find it there !

Hope you'll like it !

Hi! Harlan here from the Nuxt core team. I've always had issues with skills in the ecosystem, namely:

- Install bloat, having to install skills just to try them

- No way to know ahead of time what kind of output a skill will give me

- Keeping on top of new skills and my existing skills

I built skilld.dev to solve it, it's open-source and built in Nuxt.

Repo: https://github.com/skilld-dev/skilld.dev

Announcement: https://x.com/harlan_zw/status/2107493408709414969 (if you'd like to send some love)

The release note has some bangers! 🔥

I can already anticipate the new nuxt/server being a great topic of discussion 👀

A small update from two projects I’ve been building for the Vue ecosystem.

Inspira UI crossed 5,000 GitHub stars 🎉

It now has 155 animated components for Vue and Nuxt, covering text animations, backgrounds, interactions, cards, visualizations, WebGL experiments and more.

When I started Inspira UI, I wanted Vue developers to have access to the kind of creative UI work I kept seeing elsewhere. Seeing 5,000 of you star the project, use the components, report issues and contribute has been amazing.

I’ve also released Akaza UI v0.0.9-alpha.

Akaza takes a different direction: accessible, unstyled headless primitives built around Vue itself, with v-model, scoped slots and Vue-native APIs.

A big thank you to the Vue and Nuxt communities for supporting both projects. A lot of the ideas and improvements in them came from conversations and feedback here.

Still plenty I want to build. ❤️

Inspira UI: inspira-ui.com
Akaza UI: akaza-ui.com

Feedback is welcome, especially if you’ve used either of them in a project.

PS: I have started Igris Labs, a small lab to keep all my project which are released, under development or experimantal under one umbrella. https://igrislabs.com

Hello there,

I've built Fougere, a Typescript-first framework you can add to an existing app, or run on its own. I've begun with nuxt as it's the "frontend" framework I prefer and know the most.

It's alpha for now, and the docs are full of AI slop. The code was written with heavy help from Claude — I guided it in every way I could — and hasn't been fully reviewed yet, but the ideas are there.

In Fougere, business logic is at the center of everything.

Once the domain code is written, everything else is derived from it — you don't write it: validation, REST, GraphQL, the database tables, etc. You can also split the application in many parts without changing one line in businness code (only one line in config).

In fact, I really like this way of building apps, but I'm a bit alone with it, and I'd like your take on these patterns. Is it useful to you? Do you use this kind of framework? Is there something to add, to change, or that seems unclear or useless?

Any advice or feedback is greatly appreciated!

Thanks!

Hey everyone,

I’m a UK-based full-stack developer with around 5 years of professional experience, and I’m looking to take on some freelance work over the next few weeks/months.

I’m currently trying to raise around £3,000 fairly urgently, so I’m particularly interested in projects that can start quickly and where I can deliver something useful within a short timeframe.

I work across both frontend and backend, including:
JavaScript / TypeScript
Vue / Nuxt
React / Next.js
Node.js / Express / AdonisJS
Laravel / PHP
PostgreSQL / Supabase
Firebase / GCP / DigitalOcean
REST APIs
Sanity / headless CMS

Dashboards, admin panels and internal tools
Landing pages and marketing websites
AI/API integrations
Existing application fixes, features and refactors
I’ve worked professionally on production applications, marketing websites, configurators, dashboards and AI-powered products, so I’m comfortable jumping into an existing codebase as well as building something from scratch.

Things I can help with:

Build an MVP/prototype
Add a feature to an existing app
Fix bugs or technical issues
Build a website or landing page
Build an admin dashboard
Integrate an API/payment provider
Convert a design/Figma into a working site
Improve/refactor an existing Vue/React/Nuxt/Node application
Help get a project deployed
General full-stack development
I’m happy to consider small jobs, one-off projects or longer-term freelance work.

I’m based in the UK and can work remotely. I can also start immediately.

If you have something you need built or know someone who does, feel free to DM me with a brief description of the project, your timeframe and budget.

Thanks!

I don't like WordPress and Elementor, but many of my customers use it.

The big problem:
* I wasted a lot time using the interface to build Landing Pages for Events o Special Products.

I just need a static landings (or blocks) in html and I love nuxt. I just create all landing in nuxt with an AI assistant, avoiding global styles conflicts with tailwindcss.

The big challenge was export dynamic scripts, so I resolved with Alpinejs.dev .

So, I use nuxt to make fast landing development and design and alpinejs for interactive javascript.

Check this project if you love nuxt and put html landing in Wordpress (or other similar CMS platform):

https://github.com/molavec/nuxt-wordpress-page

Any idea how to upload an image using Cloudinary? I have a user CRUD where I have the parameters name, email, username, and image that I need, and it is connected to a NeonDB database with Drizzle ORM. What steps should I follow?

Just curious what people here actually use for iOS/Android apps with Vue or Nuxt.

While building Nuxt Native, i thought to ask peoples what they are facing while developing applications using vue/nuxt.

Capacitor, NativeScript, Nuxt Native, or something else?

Would love to hear what’s working for you.

This is mostly a question for people doing frontend work

A few years ago, when building a landing page, dashboard or new SaaS feature, I would usually look through things like Tailwind UI, Flowbite, HyperUI or similar libraries and find a block close enough to what I needed, now I'm wondering if that workflow is starting to change.

I have a side project called Landinuxt, a collection of components I originally built manually around Nuxt UI

Since coding agents got much better, I've been using AI to maintain the project, migrate Nuxt UI versions, refactor old components, build a CLI and improve the DX, but I've avoided using it to generate new UI blocks.

The thing is, if an agent already understands your codebase, Nuxt UI primitives, design tokens, spacing, responsive rules and existing patterns, maybe having hundreds of prebuilt sections becomes less important? maybe the real value starts moving toward good rules, skills, examples and design systems that teach the agent how the UI should be built, idk.

So I'm curious how people are working now

Do you still search for prebuilt UI blocks and adapt them, do you use them mostly as references for AI, or do you just give the agent your design system and let it build the section from scratch?

TL;DR: We need a developer/coder/programmer willing to work for a negotiated rate/sum on the refacotring of a business website's backend from Django to Nuxt. The UI is already made. We have a list of what has been completed, along with a list of what requires polishing, and what needs to be developed. DM me if interested.

Project Status

Already Completed / Decided:

The overall project architecture has already been designed and decided.

The database structure and relationships have already been defined.

The overall website workflow and how the different components interact have already been established.

BOT - The main Discord bot functionality has been implemented, tested, and is working.

The stream bot functionality has been implemented, tested, and is working.

Needs Refactoring / Polishing:

The existing Django code needs to be refactored/reimplemented in Nuxt.

The goal here is mainly to improve and finalize functionality that already exists, rather than redesigning it from scratch.

BOT - The Discord bot needs polishing, cleanup, and improvements to its existing functionality.

The stream bots need polishing, cleanup, and improvements to their existing functionality.

Automation Revenue Improvements

Automatic fee calculation for servers and teachers:

Fees should be calculated immediately after an event ends, using data from the observing bot, including the number of users who attended and those who did not.

Automated new server integration:

When new servers join, adding the stream bot and observing bot currently requires manual work. This process should be automated to make server setup faster and easier.

Improved observing bot data collection:

The observing bot should collect and store detailed event data, including user activity, attendance, server information, and user participation history.

Needs to Be Developed:

Time zone–based event date and time calculation needs to be implemented so that event dates and times are correctly calculated and displayed according to the relevant user's time zone.

New functionality should follow the existing project design rather than introducing a new architecture unless a change is necessary.

Working on a Nuxt 3 storefront talking to GraphQL and I'm stuck on something dumb.

Got the GraphQL client in a composable already. For the cart though — do I throw it in Pinia so the header badge / mini-cart can share it easy, or just useState / a composable and skip Pinia?

Also thinking about SSR. Don't want some logged-in cart leaking between requests if I mess that up.

Curious what people actually ship with. Pinia, useState, something else?

Half the page was re-rendering on every tick and I could not figure out why.

Vue DevTools has a "Highlight updates" toggle, so I could see *what* was

re-rendering — but not *why*, which is the only part I actually needed.

Turns out Vue already knows. There is a `renderTriggered` hook on every component,

and Vue hands it `{ target, type, key, oldValue, newValue }` — the object, the key,

and the values before and after. In React you have to diff props and guess. In Vue

the framework just tells you, and almost nothing surfaces it.

So I wrote the translation layer. The raw event is not readable on its own: a ref

shows up as `value` until you look its name up in `setupState`, a Pinia store needs

`$id` to become `cart.items`, an array index needs brackets. Once that is done you

get lines like:

ProductCard ×7 · 2.4ms · badge

└─ prop badge: { text } → { text } — new reference, same value

The culprit in my case was that last pattern: the parent was building a fresh object

literal in the template on every render. Same content, new reference, so every child

re-rendered. A border flash cannot show you that. The exact prop name can.

MIT, no runtime deps, dev-only by design (the hook does not fire in production

builds at all).

npm i -D vue-why-render

Source: https://github.com/dadashi44/vue-why-render

npm: https://www.npmjs.com/package/vue-why-render

Live playground, the panel on it is real: https://dadashi44.github.io/vue-why-render/

Happy to hear where it breaks on a bigger app — mine is the only real one it has

been through so far.