The components are presented without design at all

[meirlamdan]

I installed the library The components appear But without any design

I get a warning about tailwind-merge

Is it maybe because the configuration of tailwind-merge is not compatible with the current version?

[itsJohnnyGrid]

Hi, @meirlamdan could you try to install the latest version of the packages and check if the issue still present:

• npm i vueless@latest
• npm i @vueless/plugin-vite@latest

And also provide more details about your environment / package manager etc.

And please check this alsо: https://docs.vueless.com/#minimal-requirements

[meirlamdan]

"@vueless/plugin-vite": "^0.0.74", "vueless": "^0.0.433"

Operating System: Windows IDE/Text Editor: Visual Studio Code (VSC) Shell: Bash Package Manager: npm

[meirlamdan]

The mistake was that I left the default setting in tailwind.config.js

content: [
    "./index.html",
    "./src/**/*.{vue,js,ts,jsx,tsx}",
  ], theme: {
    extend: {},
  },

Maybe it should be highlighted in the documents

[itsJohnnyGrid]

@meirlamdan I guess you forgot to add vuelessPreset into your tailwind.config.js. See step 3 in the docs here. This config already set there to make the configuration more easier.

If the issue persists after that, please let us know.

[meirlamdan]

I set it right But I also left the section below

content: [
    "./index.html",
    "./src/**/*.{vue,js,ts,jsx,tsx}",
  ], theme: {
    extend: {},
  },

[itsJohnnyGrid]

I set it right But I also left the section below

content: [
    "./index.html",
    "./src/**/*.{vue,js,ts,jsx,tsx}",
  ], theme: {
    extend: {},
  },

Could you share the full file of your tailwind.config file please?

[meirlamdan]

/** @type {import('tailwindcss').Config} */
import { vuelessPreset } from "vueless/preset.tailwind.js";

export default {
  presets: [vuelessPreset],
  content: [
    "./index.html",
    "./src/**/*.{vue,js,ts,jsx,tsx}",
  ]
}

If I don't remove these lines:

  content: [
    "./index.html",
    "./src/**/*.{vue,js,ts,jsx,tsx}",
  ],

then there is the problem

[itsJohnnyGrid]

@meirlamdan I'll double check this and let you know, thanks. By default it should work without content config property.