Konrad

you can try dynamic import: ``` components: { CookieLaw: () => { if (process.client) { return import(/* webpackChunkName: 'vue-cookie-law' */ 'vue-cookie-law') } }, }, ```

Config was: latest Nuxt 3 with Vite + latest Windi. Unfortunately, there were many more issues we've stumbled upon (other than WindiCSS) so for now, we've given up with Nuxt...

> ... Disable page tracking in the config... This is counterintuitive. I rather expect that `gtm` prop could be added on the page with property `pageUrl` containing the desired path....

@matt-jay Indeed striping semicolons through regex is possible at the GTM level. Thanks for the tip. But this is not so straightforward for errors, because in Nuxt errors layout it...

So to sum up my experience: - can't use `lang="postcss"` in style (webpack throws errors then) and therefore get linter errors when using long `@apply` with many classes - browserSync...

Same issue here without Sail... watch detects only the first change after starting, and then it looks that it recompiles something but no changes in output

I think there will be lots of issues with some elements changes (for example "field" class).

I suppose there are issues with update Bulma's package, but sticking to Bulma 0.3.x cause this admin to be more and more obsolete.

It was just bumped to 0.5 / 0.5.1 with lot of changes - classes especially.

No. We've dropped VueAdmin as this project is not reliable anymore. We're using another admin based on BootstrapVue that is far much better maintained.