Vjacheslav Trushkin

Thanks. This is weird error message. In `.js` file Rollup created wrapper for `require()`, which could have been causing issues, but in `.mjs` file there is nothing that could trigger...

I've debugged this. Component works correctly with NextJS 13 without any issues. I've also reverted change to see if I'll get that error message, didn't get it. So I can't...

Thanks a lot! Now I'm seeing that bug and can debug it. This is very helpful!

I'm very confused. In your code `React.Component` does not exist. Icon component is fine. It uses React in intended way, but something else is messing with it. Somewhere in build...

One more weird thing: I've installed React `18.2.0`. It is installed correctly, I've checked files. However, in component when logging `React.version`, it returns `18.3.0-next-4bd245e9e-20221104`. So there seem to be a...

React is imported from this file: `node_modules/next/dist/compiled/react/index.js`, however, that file contains everything, including `Component`, but for some reason it does not exist in imported file. I suspect Webpack is to...

I can't find anything in Next documentation that states that class components are not allowed.

Indeed. Same when importing it in console. But add this to top of `node_modules/@iconify/react/dist/iconify.mjs`: ```js console.log('Imported React. Keys:', Object.keys(React)); ``` and it will show short list.

With `"use client"` in component, it throws errors about missing "private-next-rsc-mod-ref-proxy" module.

So it is not Webpack's fault. Found where stuff is missing: React is not being imported from file I've mentioned above, but from `./node_modules/next/dist/compiled/react/cjs/react.shared-subset.development.js` and it is missing `Component`. Looks...