miguelrk
miguelrk
Thanks for the quick answer! I totally understand, Vuetify 3.0 is the main bottleneck here. I would also agree that maintaining 2 versions of the lib might be too much,...
Thanks! I see your points, and yeah, now that you say it it might indeed be better to have a retro-compatibility branch for a while and then drop it. I'm...
Hey @suraj740! The wait for `vuetify3` ended up being longer than expected, therefore this issue got sort of pushed back. But `vuetify3` is now almost feature complete (`RC` is very...
Great! I think I would wait for at least the `RC`, or some more major components like `v-data-table` to be in `vuetify3` to start the fork. But I would be...
**FYI:** just opened PR https://github.com/denoland/fresh/pull/1303 which adds a `unocss` plugin based on the new `renderAsync()` method 👍🏼
Starting from [[email protected]](https://deno.com/blog/v1.28), npm compatibliity is now marked stable. I've successfully migrated some Node.js projects to `deno` and adding npm prefix to `import {} from "npm:package-name"` with `import_map.json`. What in...
Thanks for the thorough overview @apollo79 ! I will stick around 👍🏼
Thanks for summarizing this in an issue @tvld. This has made me understand your points better, here is what I think: - **Separate hooks-file per service**: I agree. Hooks tend...
Any news on this? Not only is having to use `.list()` suboptimal performance wise (having to read keys AND values into memory) but also cost wise (on Deploy). +1 to...
+1 for adding object storage to Deploy and Subhosting