Migration to v3

[jawnothin]

Description

Is there a recommend way to upgrade from v2 to v3, that doesn't involve committing to converting the entire project over all at once? Or is there a way to run both v2 and v3 at once so that we can iterate our way into the migration?

[benjamincanac]

It isn't possible to have multiple versions of the same package no. You can follow our migration guide to upgrade your project from v2 to v3: https://ui.nuxt.com/getting-started/migration

[jawnothin]

It isn't possible to have multiple versions of the same package no. You can follow our migration guide to upgrade your project from v2 to v3: https://ui.nuxt.com/getting-started/migration

I was afraid of that .. that's going to make the migration quite painful as it could cause all development to come to a screeching halt depending on how many changes need to be made.

[benjamincanac]

As explained in the documentation, Nuxt UI v3 is a new library that has been rebuilt from the ground up. You can read more about this here: https://ui.nuxt.com/getting-started#migration

[jawnothin]

As explained in the documentation, Nuxt UI v3 is a new library that has been rebuilt from the ground up. You can read more about this here: https://ui.nuxt.com/getting-started#migration

Oh I know I'm aware, that's why I never adopted the alpha version, I was hoping that wasn't going to be the case with the final release. Having some sort of compatibility mode could make the migration easier to digest, such as having a different prefix for the components, or perhaps even v2 supporting tailwind v4 could be helpful as well, so then you could in theory get v2 to tailwind 4, then import the v3 in compatibility mode, slowly migrate things over without having to do it all in 1 shot. I don't think I speak just for myself, but someone with a very large project may never update to v3 because the effort is just too difficult and prevents moving forward on anything else until it's done. Or if you do move forward you're constantly having to merge in charges from your main branch would could lead to significant conflicts.

[benjamincanac]

I understand the problem but we won't implement such compatibility mode nor handle Tailwind v4 in Nuxt UI v2, the two version are simply too different. I guess you can stick with v2, we'll keep supporting it.