Is there a bug in @googlechrome in Android and HTTP Client Hints when requesting the viewport size? I'm using them in my @vuetifyjs@nuxt_js module and it is not working properly.
On my Samsung Galaxy S22 Ultra, I'm receiving this headers:
I hadn't tried the @vitest_dev in-source testing yet, it is the perfect match for the new @vite-pwa/assets-generator api (with dead code elimination on build):
Logic updated in pwa docs, now you can open the diagram directly in @excalidraw (removed download link).
There is a new injectManifest diagram with some reference to meta frameworks and updated some errata.
Thx again @aakansha1216
It seems that filtering duplicated splash screens dimensions before generating them, we'll finally end up with 15 distinct splash screens, but we still need to add 15KB to each html page when using dark and orientation variants:
Sorry @nuxt_js (Docus), but I'm completely in love with the VitePress theme by @KiaKing85 , I'm using VP for the vuetify-nuxt-module documentation website:
Released a new vuetify-nuxt-module version (v0.4.4) with Nuxt Layers and Nuxt Hooks support, a few bugs fixed and improved DX for directives, global components and lab components configuration.
New releases for vite-plugin-pwa (0.16.4) to include more web manifest options and @vite-pwa/vitepress (0.2.0) updated to use new types in VP beta.2 (breaking changes).
For example, using new @MSEdgeDev side panel manifest option:
Released SvelteKitPWA v0.1.0 with @vite_js 4.0 and @sveltejs kit 1.0.0 support and VitePress PWA v0.0.3 with @vite_js 4.0 support.
We are also finishing Zero Config PW for @nuxt_js 3: stay tuned.
Check the docs here:
vite-pwa-org.netlify.app/