How to use WireUi with Vite

Did you update your tailwind config as explained here? https://livewire-wireui.com/docs/get-started

@Sinnbeck Yes I update the tailwind configure file and theres no errors in the console. On version Laravel 8 everyting was workings fine. After update to Laravel 9.2 with Vite this issue is happend.

@skreng can you show your resources/css/app.css and tailwind config

Did you run npm run build?

@Sinnbeck

tailwind.config

const defaultTheme = require('tailwindcss/defaultTheme');

module.exports = {
    content: [
        './vendor/laravel/framework/src/Illuminate/Pagination/resources/views/*.blade.php',
        './storage/framework/views/*.php',
        './resources/views/**/*.blade.php',
        './vendor/wireui/wireui/resources/**/*.blade.php',
        './vendor/wireui/wireui/ts/**/*.ts',
        './vendor/wireui/wireui/src/View/**/*.php'
    ],

    theme: {
        extend: {
            fontFamily: {
                sans: ['Nunito', ...defaultTheme.fontFamily.sans],
            },
        },
    },

    plugins: [
        require('@tailwindcss/forms'),
        require('@tailwindcss/aspect-ratio'),
        require('@tailwindcss/typography')
    ],
    presets: [
        require('./vendor/wireui/wireui/tailwind.config.js')
    ],

};

app.css

@tailwind base;
@tailwind components;
@tailwind utilities;

Nope I have run only npm run dev

@skreng try with build first to see if it compiles

@Sinnbeck Yes I have 2 files.

But every label in the login/register form disappear and no reaction on click login/register button. No error in the console.

@skreng ok looks like it's missing some text classes, but some of it is working. Inspect the elements to see what is missing

@Sinnbeck But why it disappeared when the package wireUI is install. If I uninstall everyting is OK.

@skreng I have never used it so I cannot say sadly. I don't use livewire/alpine myself :)

@Sinnbeck Silly thing. I realize that Laravel use login and register forms components <x-input> and <x-button> And the WireUI also use the same component name <x-input> and <x-button> but with different params. Just need to change the Laravel component uses on normal input or button and everything is OK.

@skreng ah exelent :)

@skreng do you mind sharing? I cloned LaravelDaily/Livewire-Wizard-Demo and exactly the same thing is happening to me.. haha

@laastos This was exactly the issue for me, a collision in the component naming. Thanks