teamboot88

I think it's a critical issue. When can it be modified?

Currently, I show it only when the pending value of lazyFetch is true, or I am detouring it with the `ClientOnly` tag. Is there a better solution?

- workaround works in 3.1.1 only. - in 3.1.2, the below error occurs ``` [nuxt] [request error] [unhandled] [500] require is not defined in ES module scope, you can use...

------------------------------ - Operating System: `Windows_NT` - Node Version: `v16.19.0` - Nuxt Version: `3.2.2` - Nitro Version: `2.2.2` - Package Manager: `[email protected]` - Builder: `vite` - User Config: `-` - Runtime...

I checked that it was resolved on the edge channel. Thank you very much for your quick feedback.

This is not resolved. I'm using edge channel.

I found the part that caused the error. Occurred when adding a nuxt-proxy module and using the proxy option. https://github.com/teamboot88/reproduction

I have same problem..

Support for dark mode would be greatly appreciated.