HummingMind

Results 34 comments of HummingMind

Also, Things seem to work better with fontsource as the provider, instead of google. At least I get the correct subset and format loaded. 🍻

This might be a bug with Nitro (or one of its dependencies) used by Nuxt. Submitted a [bug report](https://github.com/unjs/nitro/issues/2523) there.

> > Allow to control which assets are compressed. Something like {formats: [html, svg, js, css]} > > What's the usecase for that? Probably not as important as # 1...

> > Looks like html, js, json, css, svg, xml are currently compressed. > > Actually the code has `['.html', '.js', '.mjs', '.json', '.css', '.svg', '.xml', '.wasm']`. Yes, it could...

Deprecated warnings are gone in version 2.0.0-rc.0 that was just published.

> @HummingMind are you using NuxtDevtools? Try to disable `componentInspector` inside `nuxt.config.ts`: > > ```ts > devtools: { enabled: true, componentInspector: false }, > ``` > > I think this...

Some info: [Article 1](https://www.steffenstein.com/blog/how-to-solve-extraneous-non-props-attributes-in-vue-js/) [Article 2](https://zelig880.com/how-to-solve-extraneous-non-props-attributes-in-vue-js)

@zernonia ![image](https://github.com/user-attachments/assets/8756018f-5a37-409e-97a5-dac4a73d2e17) nuxt config: ![image](https://github.com/user-attachments/assets/4db5d7f5-f5ca-41db-af42-139cb0cbeb97)

@zernonia awesome! I think it's an important fix, as many people use the component inspector in the Nuxt devtools. Thank you for all your hard work!

@zernonia just FYI, looks like antfu released nuxt devtools 1.5.2, which downgrades the vite-plugin-vue-inspector to an older version that does not cause the warnings to come up. So I can...