Dylan Vos
Dylan Vos
@tofandel In my case, it doesn't go into the vendor.css - but it's included inside the .js file... I am doing a mix-extract as follows: ```Javascript .extract(['vuetify'], 'js/vendor/vuetify.js') ```
> So the problem is caused because there is 2 MiniCssExtract plugin, the second addition is not needed, there should be a check, if it's already present in the plugins...
I changed it to the following, `extract` is now just a simple boolean - and both, the CSS and JS are getting extracted correctly: ```Javascript const mix = require('laravel-mix') const...
Any update on this? It's almost three years later and this is almost the only thing I can find about it
It will mostly be a single-day-a-week effort I can put in, because of work, but at least it will be worked on! I will focus on the `org.openhab.ui` - this...
I will start with the pure upgrade first - saw there are tests or at least a framework for it - so will check that out first A question though,...
Ah good to know - when I have time I'll go through the code (created a fork) and sum up what to do in a pull request so we can...
> As the MainUI code needs to be changed anyway when switching from SSE to WebSocket, it could probably be done in a way where the MainUI code itself does...
Quick question, maybe I missed it - but is there a contribution guide?
~Is it within scope of this to also move to the latest recommended build stack for Vue? So move from webpack to Vite?~ n.v.m. that - I will first do...