Vjacheslav Trushkin

This can't possibly be intended by design. Very weird. I've reported this as bug to Next repository, including your demo repository: https://github.com/vercel/next.js/issues/43051

Oh well, got response from NextJS team, missing support for class components is by design. Looks like for now your solution with wrapper component is the only way to make...

Reported issue for web component not being bundled, based on your repo: https://github.com/vercel/next.js/issues/43068

Depends on which part of issue you are referring to. If using `@iconify/react`, that is intended by NextJS design. It needs to be wrapped in client side component like in...

It won't render anything on server side anyway, so forcing it to render on client side doesn't make any difference. This component works by loading data dynamically from API, which...

You probably forgot to import `iconify-icon` (or `@iconify-icon/react` if you are using React wrapper), so web component didn't get bundled.

In browser console type `customElements.get('iconify-icon')` It should return class for web component. If it doesn't return it, web component is not bundled.

I'm not sure what you are trying to do there, but you are most likely doing it wrong. That icon has no text nodes, so setting `font-size` doesn't make any...

Actually, you are correct. While older docs refer to it as applicable only to text elements, newer spec allows it on any element, so it should be usable on ``...

Tested, have same issue. No special characters in path. MacOS 14.3.1 Node 20.5.0 Yarn 3.6.0