SerKo

@manniL i was wondering if it is possible to add an option to ignore the warning message?

@steveulfelder Thanks for sharing the solution and I totally agree your notice. However, by using Nuxt's `ssr: false` option to develop an SPA, you can also enjoy Nuxt's excellent DX....

I just drafted a PR (#88) to implement escape for `unflatten`. However, I need some assistance on `stringifyFrontMatter` and `stringifyCodeBlockProps`. Are any maintainers available to take a look? Your help...

@userquin Thanks for advice, I have over 100 custom icons so I use `customizations.iconCustomizer` for replacing the `width` and `height` props for temp fix now.

> Can you give a failing test first? I am not sure if the original behavior is actually desired (maybe the docs need to be improved instead). @antfu I created...

Just submitted a draft PR (#4089) that contains failing tests. Currently investigating on the `loadIcon` behavior in `@iconify/utils` to see if any solution ideas on `presetIcons`.

### Summary of the current research progress: The issue started with the following commits: https://github.com/iconify/iconify/commit/439a862a1a0f0679038a0272bf06a9f277a50756 https://github.com/iconify/iconify/commit/412c8119b0e1b1a48e58304181d4b4798d59c697 ```diff - props[prop] = `${scale}em`; + props[prop] = calculateSize( + // Base on result...

@antfu @cyberalien Thank you! Fixing it through `@iconify/utils` does seem more appropriate. By the way, I had earlier attempted to address the issue through `@unocss/preset-icons` and managed to resolve it...

@cyberalien How about making it optional?

@userquin Oh! Thanks for the reminder. I’m currently researching whether there’s a way to reduce build memory usage (it does require more than 16GB at the moment). So, it’s still...