patak

/ecosystem-ci run

After https://github.com/vitejs/vite/pull/16471/commits/2866d4f2f6cbd184c9d94bc0cdda3c79e790b1aa, we have opt-in for build plugins to be shared, matching the way things work during dev. Individual plugins can set a `sharedDuringBuild: true` to opt-in, or all plugins...

> It feels really nice to use, so only positive feedback here to confirm if I'm using it right: > > * since `create(environment)` provides `environment.mode: "dev" | "build"`, I...

> Indeed, calling `this.environment.hot` during `transform` where the tokens are extracted can work normally, but it was a reminiscent of the original unocss plugin as it provides asynchronous `onInvalidate` listener,...

We discussed with @sapphi-red and he proposed we move away from the `create` hook for bounded plugins, and use a factory (both Anthony and me preferred this form too initially)....

/ecosystem-ci run

I think we should go with url here. It feels a bit too much to have both `clientFiles` and `clientUrls` though. I wonder if we could keep only the urls...

About Nuxt, it is also failing in main right now.

@sodatea should we be able to use `vue` (for example only the reactivity system) without the vite plugin? Or does the plugin needs to be always there for Vite from...

Thanks for testing @jacekkarczmarczyk! cc @userquin in case this rings a bell