-
Notifications
You must be signed in to change notification settings - Fork 631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v3 #1289
Comments
I would like to help, if I'm able to. Is there going to be a dedicated branch or will it be done in the |
Once we start this, there will be indeed a new branch with auto-release so we can try it out and especially keep working on the |
I have few design ideas if you are open to this I would like to share it for the future of Nuxt UI 3. Should we discuss this in this issue or it'll be better to discuss design ideas in seperate discussion thread? |
@jd-solanki You can share them here! |
Since it is supposed to be a refactoring to all components, could we give the possibility of compatibility with unocss? |
@sawa-ko It will be made with Tailwind v4. To what end would you make it compatible with Uno? |
I've started working on this in a private repository of mine, I'll open-source it once I'm satisfied with the base so you guys can check it out 😊. A lot has changed since I'll post regular updates on this issue. |
Please tell me how long it will take for this upgrade to be available. |
I have no idea how long it will take and it's not entirely up to us, I hope to release it at the same time as the official release of Tailwind v4. |
That's awesome. The new version of nuxt-ui uses exactly the tech stack I expected. I tried to build my own UI library using radix-ui and tailwind-variants, but I immediately found that even with radix-ui, it is not easy to build a full UI library. But I got an idea with an API that works with any design language. If you are interested, here is my demo repository: |
@robin-dongbin It's already in the making. There are already 13 components done, 36 more to go 😅 |
Since the component library is based on radix-ui without styles, I thought it would be nice to provide an api that is abstracted from various design systems, so you can switch styles from one system to another at any time. If people want to implement another design system, they can just customize it, share files, or even contribute to a repository. Taking things a step further, it is possible to switch between different design systems at runtime. Of course, I'm just offering an idea, and if you think it's too late, that's fine |
This is actually already what we're doing with the App Config. You can customize the classes for every part of every component. |
Thanks for the work! Just one question :
|
No we keep the For example the export default {
base: 'inline-flex items-center justify-center text-gray-900 dark:text-white',
padding: 'px-1',
size: {
xs: 'h-4 min-w-[16px] text-[10px]',
sm: 'h-5 min-w-[20px] text-[11px]',
md: 'h-6 min-w-[24px] text-[12px]'
},
rounded: 'rounded',
font: 'font-medium font-sans',
background: 'bg-gray-100 dark:bg-gray-800',
ring: 'ring-1 ring-gray-300 dark:ring-gray-700 ring-inset',
default: {
size: 'sm'
}
} Here is the new version: export default {
base: 'inline-flex items-center justify-center text-gray-900 dark:text-white px-1 rounded font-medium font-sans bg-gray-50 dark:bg-gray-800 ring ring-gray-300 dark:ring-gray-700 ring-inset',
variants: {
size: {
xs: 'h-4 min-w-[16px] text-[10px]',
sm: 'h-5 min-w-[20px] text-[11px]',
md: 'h-6 min-w-[24px] text-[12px]'
}
},
defaultVariants: {
size: 'sm'
}
} This is a breaking change if you've overridden its config in your |
Ok ! Effectively, it's a breaking change but it seam ok for the future to have a better granularity with the variants. Thanks for the explanation and the example 🙏🏻 |
May be something like this : https://github.com/gigerIT/vuetify-inertia-link#readme Or like that: https://uvr.esm.is/data-loaders/nuxt |
@gitamgadtaula your file path may be too long. I was having the same issue until I moved my project directory closer to the root of my C: drive. |
@benjamincanac Can you release the alpha 12 with the Tailwind v4 ? 😄 |
@bocooper-dev What OS are you using? I got the same error and this is blocking using a better way for #3177 😅 I'm on Windows and my path is short |
MuhammadM1998 I'm using windows as well. Originally my project was in my OneDrive folder. When I tried to reproduce the error here on codesandbox, everything worked flawlessly. So then I tried copying files into my OneDrive project and got a windows error message about some file paths in node_modules being too long. Once I re-cloned the project to my C: drive, I no longer had issues. If things still aren't working for you, you can also try increasing the Maximum Path Length Limitation in the Windows Registry. |
@bocooper-dev Thanks for the insights 🙏 I'll try that and get back to you |
@bocooper-dev @MuhammadM1998 Or, in alternative, use WSL. But if you want to talk about this feel free to start a discussion on Nuxt's Discord server and tag me in, I'll try to help as I can. |
Could we get an example of using a UCard in a radio group? Seems like we can't in this new version? |
@BlackDahlia313 A PR is underway to add the variant! #3178 |
Haha well would you look at that! insert meme here How awesome! Thank you! (I should have checked PRs first haha) |
Hello, is there any way to use I solved the hover effect by adding this
would be nice to understand how to make the full row as link Thanks. |
This would actually be really good also for possible prefetching. |
Do you have an estimated release date for Dashboard components for v3? Awesome work! Thanks! |
Clickable table rows came up a lot of times already and I would also REALLY appreciate this! This might be the right PR to upvote I guess: |
@bocooper-dev @MuhammadM1998 try to install typescript to your dev dependencies. |
Hi @benjamincanac, Is there a rough timeline when we can expect a beta or v3 release? I can imagine that it's quite a lot of work, especially that TW 4 now has been released. It's not to push, but just to make an internal decision within my company if we would already move over to Nuxt Content. One of the issues we now have for example is that Content changed the V3 is already looking great, so keep up the good work! :) |
To me it is working fine so far, definitely usable! On the other hand I see there are at least 123 open issues... |
@stijns96 I would use the The reason why it's still in alpha is because |
Hi @benjamincanac, Thanks for the update! I totally understand you want to release both and I will use alpha for now. I really like to help you guys out, but honestly I'm really busy at the moment... I'll see what I can do in the near future! |
Agreed. I am using it on a pretty complex app and it's working better from what we transitioned from that has been stable for a while. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I see comments are being marked as off topics including my own comment. I can't find guidelines as to what can be discussed in here. Would you mind providing guidelines? |
@madsh93 As mentioned previously, this issue was mostly made for news not for specific bug reports. Please open a new issue with a reproduction. |
DropdownMenu cannot be nested with Tooltip components? Code here: <template>
<UTooltip text="Copy">
<UButton color="neutral" variant="ghost" size="xs" icon="i-lucide-copy" />
</UTooltip>
<UTooltip text="Delete">
<UButton color="neutral" variant="ghost" size="xs" icon="i-lucide-trash-2" />
</UTooltip>
<UDropdownMenu size="sm" :items="exportItems">
<UTooltip text="Export as...">
<UButton color="neutral" variant="ghost" size="xs" icon="i-lucide-file-down" />
</UTooltip>
</UDropdownMenu>
</template>
<script setup>
const exportItems = [
[
{
label: 'Export as...',
type: 'label'
},
],
[
{
label: 'Markdown',
onSelect () {
}
},
{
label: 'Plain Text',
onSelect () {
}
},
]
]
</script> in this case, |
The development is ongoing on the default branch of this repository: https://github.com/nuxt/ui.
A lot has changed since
@nuxt/ui
was made open-source (May 2023), so the plan here is to rewrite every component from scratch alongside their config.I'll post regular updates on this issue and on https://twitter.com/benjamincanac.
Documentation
https://ui3.nuxt.dev
Roadmap (Nov 20, 2024)
reka-ui@alpha
on@nuxt/ui
&@nuxt/ui-pro
feat(module)!: migrate toreka-ui
#2448@nuxt/ui-pro
components@nuxt/ui-pro
components (almost all are done except for Dashboard)@nuxt/ui
likeCalendar
feat(Calendar): implement component #2618InputDate
[InputDate] Implement component #2524Tree
feat(Tree): new component #3180Stepper
feat(Stepper): new component #2733@nuxt/ui-pro
and@nuxt/content
v3 nuxt-ui-pro/saas#86@nuxt/ui-pro
v3 nuxt-ui-pro/dashboard#86@nuxt/ui
&@nuxt/ui-pro
officially oncetailwindcss
andreka-ui
are released@nuxt/ui
&@nuxt/ui-pro
componentsBreaking Changes
The biggest change is the switch to
tailwind-variants
, this will cause lots of breaking changes if you've used theui
prop orapp.config.ts
to override the config. I apologize in advance for this but I strongly believe this will be beneficial and will bring consistency across all components.The config will now have a
slots
amongst other keys that will specifically target dom nodes. Theui
prop will only allow you to target those slots.These changes alongside the refactor of all components will also improve the types, the
app.config.ts
andui
props are now perfectly typed, as well as all componentsprops
,slots
,emits
andexpose
.Components
The text was updated successfully, but these errors were encountered: