Vjacheslav Trushkin

You can achieve the same using separate CSS file with variables, as shown in example above, without triggering any bugs.

Those packages are no longer maintained. That specific package would be a CommonJS package, which should not be used in modern development process. Offline icon component was created when solutions...

It is intended behaviour. Component renders span before it is mounted to avoid breaking hydration. If component renders different content on server and client sides, it would result in React...

Probably. However, it is a new thing and compatibility is a big issue. It needs to work in recent versions of React and all frameworks based on React, not just...

After thinking more about it, I think it is time to rewrite component, targeting only latest React. Devs using older version can use older version of icon component.

Revisited this issue and just noticed that in code sample in first post it uses `@iconify-icon/react`. So I'm very confused. Issue mentions behaviour that applies to `@iconify/react`, but uses `@iconify-icon/react`...

If you want SVG content included in pre-rendered HTML, you are using wrong component. Both these components are designed to load icon data on demand. One of core functionalities is...

Would something simple, like `@iconify-react/logos` package (and similar packages for other icon sets) with exported JSX for each icon solve this? Then usage would be like this: ```ts import {...

Published new version of `@iconify/react` that is compatible with Next.js. Currently available as `@iconify/react@next`. It is a full rewrite of icon component, so need to do more testing before can...

Version 5 is now stable and published with `latest` tag. Works correctly with Next.js, no longer requires a wrapper component.