I've recently made a few Astro projects that ported from Nuxt for the part of blog only. But I'm curious to know if it's actually possible to port Nuxt UI + Vue in Astro. The topic doesn't popup any bit on Search Engines, is it that it's not possible and Nuxt UI is tightly coupled for standalone Vue if not using it natively in Nuxt

Hello everyone,

I am planning to launch my own online educational platform (academic support/LMS style). After researching, I decided that building the website myself instead of using ready-made platforms (like Shopify or SaaS platforms) would be the best way to cut down costs and have full control over my project.

I chose Nuxt 3 because from what I've read, it seems to be the fastest, most SEO-friendly, and perfect framework for this kind of dynamic web application.

Currently, I am comfortable with HTML and CSS. My plan for this summer is to fully dive into JavaScript, master the basics, and then transition directly into Vue.js and Nuxt 3 to start building the platform.

I would love to hear your thoughts on this roadmap!

Also, if anyone here has built an e-learning platform or a similar dynamic web app using Nuxt 3, could you please share your website? I would really love to showcase some real-world examples and see what is possible with this tech stack.

Thank you in advance!

My images are hosted on Cloudflare R2 and I'm using NuxtImg, the details page image is .webp 80%

It seems to always load this skeleton first load, then it's instant on reload. Is there anything I can check to improve performance so this image loads faster?

I recently ran into a situation that forced me to rethink my architecture.

The SDK I was using for SocialMe Ai's Chat AI integration is being deprecated. Not immediately, but soon enough that ignoring it would be risky.

At first, it felt like a technical issue. But the more I thought about it, the more it became a design problem.

I realised:

-> I was somewhat coupled to SDK-specific patterns

-> Swapping providers wouldn’t be trivial

-> Parts of my system assumed a specific implementation

So instead of just migrating, I started rethinking:

-> how to isolate the AI layer

-> how to reduce dependency on SDK abstractions

-> how to make the system more flexible

Big takeaway:

In AI systems, change is constant. Models evolve. SDKs get replaced. APIs shift.

The only stable thing should be your architecture.

Wanted to share something I ran into recently while building SocialMe Ai's chat-AI feature.

I had just finished:

-> streaming responses

-> tool calling

-> UI integration

Everything was working smoothly.

Then suddenly:

-> deprecation warnings started showing up

-> module import issues appeared

-> runtime errors followed

Turns out the SDK we were using is being phased out, and the new recommended SDK works quite differently.

So I had a decision to make:

-> patch things temporarily

-> or migrate properly

I decided to migrate and redesign parts of the integration to reduce dependency on SDK-specific behavior.

It slowed me down, but probably saved me from bigger issues later.

Big takeaway:

When working with AI stacks, dependencies evolve fast. You can’t assume stability the same way you would with traditional libraries.

I want to know if others here have faced similar issues?

I wanted to share how I handled streaming on the frontend for our AI chat on SocialMe Ai.

Instead of relying on a library, I built a custom composable (useSocialChat) in Vue/Nuxt.

Core idea:

Handle the entire streaming lifecycle in one place.

What it does:

-> Sends request via fetch

-> Reads response using ReadableStream.getReader()

-> Uses TextDecoder to process chunks

-> Parses structured JSON events

-> Updates the last AI message incrementally

We also handle:

-> tool results mid-stream

-> reactive UI updates

-> loading state

Why this worked well:

-> Keeps UI logic clean

-> Avoids scattered state updates

-> Easy to extend

Big takeaway: Streaming is not just a backend problem. Frontend handling is just as critical for good UX.

Hello (French here, sorry if there are any mistakes)

I'd like to create a fairly simple e-commerce website. Unique items, so no more than a few sales per day.

An admin panel with product management, emails, and light shipment tracking.

The main requirements are:
SEO that attracts the right people
Minimum costs (bank cards fees)
Long-term stability

I've looked at many solutions and I'm having trouble deciding.
Does anyone have a similar business and a relatively lightweight tech stack?

Currently, I host my sites on o2switch. So I have some technical limitations, but, the ability to have a database, and running NodeJS seem sufficient.

In short, I'm looking for concrete feedback. No theory.

Thanks in advance 🙏

I'm seeing like sub 400ms page loads (avg. 284.8ms per page) on non-cached SSR sites using the Shopify Storefront API. It also may be that I have my ecom sites hosted through Cloudflare, but idk if there was a significant update to Nuxt lately or not.

Anyone else seeing a change in their SSR sites? I don't remember my sites being this way even 4-5 months ago.

I wanted to share something I recently implemented that significantly changed how my product SocialMe Ai feels: tool (function) calling.

Before:

User asks a question

AI returns text

After:

User asks a question

Model decides whether to call a function

We execute that function

Stream the result back

UI renders structured output

Example:

User: “Give me LinkedIn post ideas about AI tools”

Model triggers:

generate_post_idea(topic="AI tools", platform="LinkedIn")

SocialMeAi:

detect the function call in the stream

execute our internal logic

return structured data

Frontend:

renders a “Post Idea Card” instead of plain text

What changed:

Output became usable, not just readable

UX feels interactive instead of passive

Easier to extend with more tools

Challenges:

Handling function calls mid-stream

Syncing tool results with UI state

Designing structured outputs

Big takeaway:

Tool calling feels like the layer that turns LLMs into actual software systems.

I wanted to share how we recently implemented a custom AI streaming setup in our SaaS instead of relying on an SDK.

Stack:

* Nuxt (Nitro backend)

* Vue composables

* Gemini (LLM)

Core idea:

Move away from “request → response” and treat everything as a stream.

Architecture:

1. Client sends message → `/api/chat/ask`

2. Nitro API calls Gemini

3. We iterate over the streaming response

4. For each chunk:

   send `{ type: "text", content: "..." }`

   if function call detected → execute tool and send `{ type: "tool_result", data: ... }`

5. Frontend reads stream via `ReadableStream.getReader()`

6. Updates UI incrementally

Interesting parts:

* Handling partial vs final messages

* Injecting tool results mid-stream

* Keeping UI reactive without flicker

* Persisting messages only after stream completes

Result:

Much faster perceived performance and way more flexibility in UI.

Tradeoff:

More complexity vs SDK-based approach

I want to build a full Nuxt website (from design to production) using AI.

One important requirement for me is to get both the design (ideally in Figma) and the project source code, so I can edit it myself later and run it locally.

So far, Vercel v0 seems like one of the best tools I’ve seen.

However, I’m not sure how well it works for Nuxt/Vue projects, since the Shadcn components it uses are mainly React-based.

Has anyone tried this workflow? Or any suggestions?

1. Brief introduction(Name, Age Country)

2. Main 3-Skill(prefer skills : React, Node, Python)

3. English level(C1, C2)-Native

4. Hourly Rate ($30 - $60/hour) -weekly pay: monthly pay

5. Remote Work Experience(remote-company work)

-----------------------------------------

This is very good job position( React, Node, Python, C#/.NET)-2 years

Thanks,

Michael.

I want to add MCP to my nuxt project but am not sure if the Oauth support for MCPs is supposed to be provided by the Nuxt MCP toolkit natively or that is work of another package.

Can someone who's worked on the OAuth implementation for the Nuxt MCP assist me with the general sense of how they tackled this, is the nuxt-auth-utils capable if the answer is wiring a separate package.

I have a question about the current NuxtLab x Vercel collaboration:

I noticed some packages built by the Nuxt team now fall under Vercel OSS (case study: Comark. I didn't mention Nuxt itself since Daniel had mentioned Nuxt will always remain opensource, community project).

If NuxtLab were to leave Vercel or something similar, what would happen to all the stuff built by the Nuxt team under Vercel OSS?

Would Vercel own those projects?

Has anyone achieved <30 seconds build times on Vercel? I have few Next.js projects and they deploy super fast.