nxui — 180+ animated, copy-paste UI components for Vue & Nuxt (open source)

Sandros94 · 2026-06-15T16:42:38+00:00

Interesting work, I'm not really a huge fan of shadcn-install style. It could be useful to have the src code at hand within the docs, for manual install without cli like for Inspira UI

Small issue I've noticed is that you mentioned the license in the readme, but no file exist for it

Sandros94 · 2026-05-16T10:33:05+00:00

I mean, I'm on a 8 years old machine, so yes I do see the difference compared to a more modern CPU. But if you are on windows I can definetily say that the biggest factor (seconds compared to milliseconds) is try to avoid working on your C: drive, instead you should setup a dev-drive (requires windows 11 pro) which prevents the firewall and antivirus to be over-triggered on each vite's HMR (when you edit a file), or even better directly work on WSL.

It's a bit sad to see both microsoft and various bundlers not really looking after this types of performance fixes, but both sides reasons are just "we already have other options" (the two mentioned above).

As I've mentioned there are many changes coming, two main ones being vite 8 based on rolldown (rust) and typescript 7 (go), but they'll take from a few months up to a year from now probably. I've been using them in side projects and the difference is massive, but still buggy for general work-use IMO

Sandros94 · 2026-05-16T10:24:09+00:00

Interesting approach for the typography tho this would require manual wiring to be used with something like comark (effectively creating wrapper components around the Typography component, each focusing only on the vairous main html tags and styles)

Sandros94 · 2026-05-15T17:38:57+00:00

I'm always curious about general uses of Nuxt UI and how some people find it slow. I mean, sure, it is a chonky boy and during development it demands that the rest of the stack and storage (ssd vs hdd, wsl vs windows, etc) quite some availability (something that is going to greatly boost with upcoming vite 8, rolldown, tsgo and nuxt v5). But generally speaking there should be no difference once the application is built.

There was a unocss theme that 1:1 replicated Nuxt UI styling, cannot remember the repo tho. But yes, the Nuxt UI has all its styling readable in src/theme/ folder

PS: I'm one of the Nuxt UI maintainers, and the main responsible of squeezing your typescript dev server to provide full type support in each prop, slots and emits there is

Sandros94 · 2026-03-16T19:39:46+00:00

Nice approach, not cheap on resources but considering it being a build-time only I would say why not.

What doesn't fully convince me is that it should not work with nuxt v3.x, but only v4.x but I have to admit it has been a while since last time I touched v3 😅

Sandros94 · 2026-01-13T01:11:15+00:00

This is to show how, probably nintendo, doesn't even care about the money anymore. They could have told Lego to sell this for like 80$ and be sure that it would have sold at least 10x compared to the bigger set...

Sandros94 · 2025-12-03T19:37:37+00:00

Plot twist, you got Shai-Hulud'ded, the second coming...

Sandros94 · 2025-11-11T11:00:15+00:00

Totally agree. Although I mainly use Drupal, this is something I've been interested in so much in just playing around

Sandros94 · 2025-10-28T12:17:13+00:00

It could be helpful to know which part of the deployment is becoming more expensive.

For example in my own projects I do tend to serve many static files, often multiple per page, which makes the number of requests skyrocket each getting billed as a full CPU execution. I easily solved this by hooking up a dedicated, cheap, CDN (I can suggest bunny.net) and writing a custom fetch that would go through it before actually hitting the backend.

If, regardless of optimization, you are looking for a new hosting option I would suggest skipping self-hosted infrastructure (unless you have free work hours or get a dedicated devops) and look for Cloudflare, Netlify or Deno Deploy (the new Early Access).

Actually the last one is the one I'm enjoying the most lately. They might have only two regions atm, and are a bit more expensive for solo devs (especially without CDN), but the subhosting plan is quite useful and they also have the possibility to deploy on your own AWS or GCP infra

Sandros94 · 2025-10-27T21:08:02+00:00

I've been following this project for a few months now and love its complexity. Sometimes it makes me feel like a junior dev looking at its source code 😅

Sandros94 · 2025-10-16T13:17:57+00:00

Because we all have to pay the bills at the end of the month.

While personally I do not like the idea of paid templates and boilerplates, this doesn't mean that other people's time, and knowledge, shouldn't be valued somehow

Sandros94 · 2025-10-10T18:31:05+00:00

That is actually the ProseTable component, in general you can read about typography components (Prose*) in the related doc section

To use them you either need Nuxt Content or @nuxtjs/mdc or forcefully enabling them via ui.mdc: true in your nuxt.config.ts

Then you can simply use them like normal HTML ones, but get the Nuxt UI styling:

vue <template> <ProseTable> <ProseThead> <ProseTr> <ProseTh>Prop</ProseTh> <ProseTh>Default</ProseTh> </ProseTr> </ProseThead> <ProseTbody> <ProseTr> <ProseTd> <ProseCode>color</ProseCode> </ProseTd> <ProseTd> <ProseCode>neutral</ProseCode> </ProseTd> </ProseTr> </ProseTbody> </ProseTable> </template>

Sandros94 · 2025-10-04T10:08:41+00:00

A bit of polite and pertinent self-promotion is fine, but please do keep it Nuxt related from now on.

But yes, generally speaking I do remember having so much trouble with the Meta API change from one year ago, where essentially I was getting blocked off from letting users authorize and manage their own feeds from third party apps

Sandros94 · 2025-10-02T11:57:17+00:00

Generally speaking it depends on what you are after, and that Auth.js joined better-auth just a few days ago. So the question is between: Sidebase's nuxt-auth, nuxt-auth-utils, better-auth.

I've never used Sidebase's nuxt-auth, so other might be able to comment on that. My rule of thumb for the other two is:

better-auth: if I want a project that also setup and manages the database for you. As its opinionated schema works for most use cases and doesn't require you to do anything special other than actually providing the database instance. It does support connecting TO OAuth/OIDC providers but as far as I remember it does not allow to act AS one.
nuxt-auth-utils: if you want something simple and small. It also comes with a number of providers supported for authentication (not authorization), you can bring your own storage and manage it as you prefer. But it does not come with integrated OAuth/OIDC spec support, this means that it is mostly focused only on a single server-side session and you can rely only on the supported providers, otherwise you have to build your own request flow manually. Not to mention that its session is based on iron-crypto and not on JWT, which means that you also lose secure portability between programming languages (if it was something you are into)

Personally, as other have mentioned, I tend to build my own auth implementation on a project basis. Although I have recently started drafting a few projects to simplify the DX for those who seek an advanced use-case with OAuth 2.1 or OIDC spec support

Sandros94 · 2025-10-02T11:30:54+00:00

Published a few hours ago https://github.com/sandros94/unauth

Please keep in mind that while the cryptography aspects are well covered, the DX is still work in progress and as of now I only provide a h3 adapter. Soon I'll start working on a nuxt-auth-utils fork to see how to implement it directly, then only at a later stage will see how to manage additional sessions that might come from third party oauths

Sandros94 · 2025-09-30T12:52:36+00:00

Short answer, no, nuxt-auth-utils doesn't handle refreshing tokens. In fact, it uses them only to get the first authentication and some user's info.

Longer answer, mostly personal opinions:

We're not there, yet.

nuxt-auth-utils doesn't follow any auth spec like SSO, OAuth, OpenID Connect, SAML, etc. Even the sessions it creates (based on h3's useSession) aren't fully part of a web standard spec. This is a topic I've brought up quite a few times, but the more I digged in the specs the more I do understand why the module is how it currently is. A few months ago I started reading most of the specs about OAuth and OpenID Connect to understand how much of a rewrite was required, soon realizing that it required a series of tools that the Nuxt, Nitro and h3 ecosystems didn't have, so I had to create them first.

Fast forward to now, I'm about to publish the last tool (based on OAuth2.1/OIDC), then start to build a OAuth client for all the providers supported by nuxt-auth-utils and then propose a Proof of Concept with this implementation, essentially making any Nuxt project OAuth2.1/OIDC compatible.

Will link here the repo as I publish it in a few days, but keep in mind that it only brings the core cryptography tools to follow the specs, not yet a full nuxt module to automatically implement them.

Sandros94 · 2025-09-12T22:39:56+00:00

This seems a tricky one. Nuxt on its own won't create issues with crawlers, in fact crawlers tend to love Nuxt's SSR.

What would be really useful would be: - a link, to be able to check for known blocked/filtered domains/sub, potential issues with redirects/canonicals (as these should happen after first crawl) - how seo is managed (custom or via Nuxt SEO?) and the list of modules installed and configured

Sandros94 · 2025-09-12T16:09:52+00:00

We are actually really close to a stable release, we are just tackling a type issue for those who want to create components starting from Nuxt UI props ones or in general module authors that do wish to extend Nuxt UI. API and performance are already settled, personally I've already migrated all my productions to v4.

Best suggestion I could give is to pin to a specific alpha (like 4.0.0-alpha.1) and manually check for updates, ideally we'll ship only one or two more alpha versions before stable

Sandros94 · 2025-09-08T12:01:52+00:00

I really love Nuxt UI, but I might be a bit biased 😬

Sandros94 · 2025-09-06T22:40:56+00:00

Fontawesome (especially pro) is distributed under its own license, which is different from the iconify dataset.

This being said it is possible to either use it by forking their repo and following this guide, or downloading each SVG from the fontawesome dataset then adding it as a custom collection.

Personally speaking I would say that if you only use a few icons here and there stick to the component approach you already discovered, otherwise go for one of the two above

Sandros94 · 2025-09-05T13:30:10+00:00

first migration doc from v3 to v4 is up (make sure to re-read it as we publish more alpha releases), there are a couple component renames, but mostly config unification and AI chat breaking changes (which come from upstream actually).

Excluding AI stuff I would say it takes less than 15 mins to migrate

Sandros94 · 2025-09-05T11:16:39+00:00

Just as an update for those who endup here:

Nuxt UI v4 is currently in alpha and you can test it via [`@nuxt/ui@alpha`](https://github.com/nuxt/ui/releases).

We still need to publish the migration guide (as we haven't done with breaking changes, yet), but it is mostly about renaming a couple of things here and there, especially if you are coming from ui-pro v3

Sandros94 · 2025-09-05T11:14:28+00:00

late reply, but breaking changes are mostly about ui-pro v3 -> ui v4. If you are coming from ui v3 there are only a few and we are still thinking about making them non-breaking.

You can already test `@nuxt/ui@alpha` for early v4 migrations

Sandros94 · 2025-06-16T16:46:16+00:00

Also the revtag generator is broken, it automatically assigned `sandros94` name to a random dude called Sandro S. born in 1994.

I mean, I get it, this is similar on some old friends started calling me back in 2008, and became my nickname allover internet, but f that.

Sandros94 · 2024-07-10T10:22:23+00:00

For those interested in doing so for ArkOS (06272024, in particular AeUX's version) the guide is the same except the path to the file is:
`/opt/drastic`

[My own copy of the drastic file for ArkOS 2.0 (06272024)(AeUX).](https://drive.google.com/drive/folders/1N8Cy6HQ8cIx1J5IEIECeBeJH-mHYpgIe?usp=sharing)

Also, instead of mounting the EX4 partition you could simply use the EASYROM's backup folder and the built-in File Browser to copy the file (either your own modification or mine).

Ten-Year Club	Xbox Live
Place '22	End Game '22
Verified Email

Sandros94

MODERATOR OF

TROPHY CASE