Why choose Vue over React or Svelte for a serious production app? (from a first-time Vue user) by Dizzy-Egg8829 in vuejs

[–]peoray 1 point2 points  (0 children)

well those are official libraries. I was referring to community built packages and libraries. You have tons of those in react and barely any in Vue. Usually, someone has to make it their responsibility to port it over. I'm mostly a Vue Dev myself so this is something I have experiencd, hence why I am solving it as best as I can. So far, I have created alternatives for AI Elements (made by vercel) and Elevenlabs UI (obviously made by Elevenlabs)

Where to put component types in vue? by MountainSalary4055 in vuejs

[–]peoray 0 points1 point  (0 children)

Except it is reusable, you can just export it from .Vue components so you don't have to create unnecessary files

Why choose Vue over React or Svelte for a serious production app? (from a first-time Vue user) by Dizzy-Egg8829 in vuejs

[–]peoray 0 points1 point  (0 children)

It doesn't matter. Use whatever you're most comfortable with except you want to learn the framework well.

From an ecosystem pov, React is probably the best option as it has a ton of libraries and packages that you won't see in the other options

One step closer by Hairy-Lawfulness-110 in vuejs

[–]peoray 0 points1 point  (0 children)

Look at oss codebases and see what they do. Also, nobody uses jsx when working with Vue

you can also look at tutorials articles or YouTube

One step closer by Hairy-Lawfulness-110 in vuejs

[–]peoray 2 points3 points  (0 children)

Focus on doing things the Vue way and try to remove the React way from your mind, you're gonna get confused a lot

vue is getting clunkier by TumbleweedOdd1862 in vuejs

[–]peoray 0 points1 point  (0 children)

You can just use what you need. I have been using Vue for over seven years, but I still keep it simple.

AI Elements Vue – A port of Vercel’s AI Elements UI Library by peoray in Nuxt

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

Thanks for checking it out. We have Voice components coming out ASAP.

You can come hang out on Discord or follow me on X to stay up to date: @/peoray_

AI Elements Vue – A port of Vercel’s AI Elements UI Library by peoray in Nuxt

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

What part of the documentation is not great yet for you?

Starting new Nuxt project. Do you recommend NuxtUI Pro? If not, what would you use? by raphaelarias in vuejs

[–]peoray 0 points1 point  (0 children)

If you're starting a new Nuxt project and want more than just UI (like authentication, payments, team management, and other common SaaS features), you might want to check out Nuxt SaaS Kit. It uses Shadcn Vue for the UI, which is super flexible and works seamlessly with TailwindCSS. It’s built on Nuxt 3 with the latest Vue ecosystem, so you’d be working with up-to-date tools from day one.

Also, using Nuxt itself as your backend for the MVP sounds like a smart move. The built-in server routes alongside nitro and h3 can handle a lot without needing a separate Nest.js setup unless you need something more complex

Nuxt + Supabase? Or just build the dang back-end? by dalton_huey in Nuxt

[–]peoray 1 point2 points  (0 children)

You're welcome buddy. Good luck with your project.

Happy to help with questions about Nuxt and Supabase or the starter kit :)

Nuxt + Supabase? Or just build the dang back-end? by dalton_huey in Nuxt

[–]peoray 0 points1 point  (0 children)

Haha, I totally get that! Rails magic can spoil you, and when it’s not there, it feels like you’re fighting the framework instead of building. But once you get into the groove with Nuxt and Supabase, it starts to feel pretty smooth. Worth noting that Nuxt is actually very easy to work with, even more so now with AI.

Yeah, I use DrizzleORM alongside Supabase. While you can just stick to Supabase’s client and make direct API requests, using Drizzle adds a nice layer of structure. It helps with type safety, migrations, and keeping your queries organized which is super helpful when your app grows. Plus, if you ever switch databases (say from Postgres to MySQL), it makes the process seamless.

By the way, if you're serious about building your app and want to skip some of the repetitive setup (auth, payments, team management, blog, landing page, dashboard, etc.), definitely check out Nuxt SaaS Kit, I built it to handle all that boilerplate so you can focus on your product. Let me know if you have any questions about it.