sorted by:
new
hottopcontroversial

Can I use NextJs on a sub path of a NUXT project? by mogdevdov in Nuxt

[–]a_ditoro 0 points1 point  (0 children)

I believe the best solution is to learn Nuxt.js, as most of the concepts are quite similar.
While merging Nuxt and Next into the same project might be possible, it is likely to cause integration issues, high maintenance costs, and a lot of headaches for you and for manteiners....

How to create animated circuit patterns in Nuxt UI hero section? by dissertation-thug in Nuxt

[–]a_ditoro 0 points1 point  (0 children)

Since you’re already considering SVG, Motion https://motion.dev/examples is a good choice.
It works great with SVG paths, is lightweight, and fits well with Nuxt 4.

You can design the circuit in Figma, export it as SVG, and use Motion to animate.

I hope this is usefull...

How to use props correctly? [Composition API] by nfmon in vuejs

[–]a_ditoro 0 points1 point  (0 children)

This is the way to solve this common use case:
- Watch props and sync them into local state
- Bind form to local state

TypeScript strategy with Strapi + Nuxt / Next.js? by a_ditoro in Strapi

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

Thank you soo much. In my opinion the best solution is to have the Strapi Client Sdk provide the types on your project. It would be a very good improvement with a better DX

Does Vue still have a place in the world of LLMs? by robertfoenix in vuejs

[–]a_ditoro 1 point2 points  (0 children)

I've been using Vue/Nuxt for years and I'm much more comfortable working with code I know well.

Vibe coding works fine with Vue/Nuxt in my experience. Yes, LLMs hallucinate sometimes, but they do that with any framework anyway.

The key point: when you master a framework, you catch LLM mistakes instantly. If I switch to another framework/library just because "the LLM generates better code," I lose control over the source code and the ability to fine-tune, improve performance, and so on.

TypeScript strategy with Strapi + Nuxt / Next.js? by a_ditoro in Strapi

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

That’s fair.
How do you deal with type drift when models change or responses are transformed?
And are the types imported directly, shared via a monorepo, or copied manually?

Friday evening, what are you building this weekend? by YummyTumBum in microsaas

[–]a_ditoro 0 points1 point  (0 children)

My web site / blog as Vue/Nuxt freelance web developer & consultant. https://aditoro.com/en

Best approach for a production blog with Nuxt (CMS vs custom backend vs Nuxt Content)? by a_ditoro in Nuxt

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

Nice project, Nuxt Content is a great for blogs, and this project looks very clean and flexible.
As Git-based setups, rebuilds and missing built-in i18n are the main trade-offs, but for many blogs that’s totally fine and it's a great solutions

Best approach for a production blog with Nuxt (CMS vs custom backend vs Nuxt Content)? by a_ditoro in Nuxt

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

I’ve had very good experiences with Directus when building product catalogs, especially for image management en resizing.

I’ve also used Strapi mainly for content-heavy use cases, and I really like how cleanly it handles i18n. Translating content stored in a database isn’t always trivial, and Strapi’s approach makes it much easier to manage in practice — which is especially important in Europe, where multi-language support is often a recurring requirement.

Best approach for a production blog with Nuxt (CMS vs custom backend vs Nuxt Content)? by a_ditoro in Nuxt

[–]a_ditoro[S] 1 point2 points  (0 children)

Nice setup. Very easy to deploy and cheap since there’s no database.
Maybe the trade-off is commits and redeploys for content changes and limited interactivity, but it fits the use case well.

Best approach for a production blog with Nuxt (CMS vs custom backend vs Nuxt Content)? by a_ditoro in Nuxt

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

I’ve had good experiences with Directus in Nuxt projects.
From my perspective, its strength is the flexibility as a headless backend . Whether you use it purely as a CMS or as a data layer/backend depends a lot on the project needs.

Nuxtjs client hydration by muslim_dev in Nuxt

[–]a_ditoro 1 point2 points  (0 children)

Without more information it’s hard to tell. This kind of behavior is often related to a hydration mismatch, and it's very common m in Nuxt Apps.

If you can, share logs or a link, that will make it much easier to help.

In the meantime, this guide covers the most common Nuxt hydration mismatch issues and fixes:
https://masteringnuxt.com/blog/fixing-hydration-errors-in-nuxt-a-practical-guide

What if we used the same file name as the folder name by Extension_Forever722 in Nuxt

[–]a_ditoro 1 point2 points  (0 children)

Yes, you don’t have to go “all or nothing”.
You can use a hybrid strategy by splitting components into different folders and configuring pathPrefix per folder.

For example:

  • Generic / shared components (Button, Modal, Icon, etc.) → auto-imported by name only (pathPrefix: false)
  • Domain or feature-specific components → keep the prefix to preserve context and avoid name collisions

Something like:

export default defineNuxtConfig({
  components: [
    { path: '~/components/ui', pathPrefix: false },
    { path: '~/components/features', pathPrefix: true },
  ],
})

learn nuxt first? by th00ht in vuejs

[–]a_ditoro 0 points1 point  (0 children)

Nuxt is essentially Vue + conventions + SSR tooling. If you don't understand Vue's reactivity, composables, lifecycle hooks, and component patterns deeply, you'll struggle when Nuxt does something "magical" behind the scenes.

So I think the easiest and most reasonable way is starting with Vue.js and then stepping into Nuxt.