kpietraszko

On the other hand, this PR doesn't build for me. As you mentioned above, it still pulls tokio because of tower and hyper, as shown in this reverse dependency tree:...

@fisherdarling WASI support is a great addition, but the use-case is a bit different. For example Cloudflare Workers don't support WASI modules out of the box, only WASM. One would...

Yeah, it's broken. Same thing on Windows, and when trying to `publish` @threepointone Did you get it working on your end, with your recent fixes?

I think there should be 2 backup types. One for coolify config, variables, etc. And another for databases. This could possible be added as a Service, for Postgres for example...

Any news on this? I think it's quite important for PostgresSQL, because - quoting the docs: > ON CONFLICT DO UPDATE guarantees an atomic INSERT or UPDATE outcome; provided there...

Sorry, I just realized `InsertOrUpdate` does exactly what I need. And it's not really relevant to this issue.

Same with :vsc Edit.GoToImplementation

Regarding the tree-shaking subject. Since preline doesn't seem to be shakable at all, using just a single component bloats the app bundle by ~140kB. I think components should also be...

> Meanwhile, you may use Preline Plugin as separate modules @jahaganiev I can, but the size is an even bigger issue then. For example importing `@preline/accordion` and `@preline/dropdown` adds 130kB...

@jahaganiev Take note of the size of those module files, they're mostly the same (large) size. It seems every module contains component+common dependencies. So when you import multiple component modules,...