R.
R.
NNuxt
Created by EmanueleDB on 3/14/2025 in #❓・help
Nuxt UI 2.21.1 migration to v 3.0.0
in css using variables and related rules
89 replies
NNuxt
Created by EmanueleDB on 3/14/2025 in #❓・help
Nuxt UI 2.21.1 migration to v 3.0.0
89 replies
NNuxt
Created by EmanueleDB on 3/14/2025 in #❓・help
Nuxt UI 2.21.1 migration to v 3.0.0
make sure that related packages are installed
"tailwindcss": "4.0.14",
"@tailwindcss/vite": "4.0.14",
"tailwindcss": "4.0.14",
"@tailwindcss/vite": "4.0.14",
89 replies
NNuxt
Created by EmanueleDB on 3/14/2025 in #❓・help
Nuxt UI 2.21.1 migration to v 3.0.0
you don't need any tailwind.config or tailwindcss options in nuxt.config in v4, just css, like
@import "tailwindcss" theme(static);
@import "@nuxt/ui";

@theme {
--color-colorname-50: ...;
...
--color-colorname-950: ...;
}
@import "tailwindcss" theme(static);
@import "@nuxt/ui";

@theme {
--color-colorname-50: ...;
...
--color-colorname-950: ...;
}
89 replies
NNuxt
Created by enricopolanski on 7/11/2023 in #❓・help
Is there a way to debug _which code_ is changing a `ref`?
It'll be still visible at the breakpoint catch
7 replies
NNuxt
Created by enricopolanski on 7/11/2023 in #❓・help
Is there a way to debug _which code_ is changing a `ref`?
Had the same problem, temporarily did this and looked at the call stack. Not ideal, but...
const _variable = ref("some_value");

const variable = computed({
get: () => _variable.value,
set: nextValue => {
debugger;
_variable.value = nextValue;
}
});
const _variable = ref("some_value");

const variable = computed({
get: () => _variable.value,
set: nextValue => {
debugger;
_variable.value = nextValue;
}
});
7 replies