Louis Lin

Results 3 comments of Louis Lin

I'm also encountering this error and using Next.js (as @d-ivashchuk suspected). My workaround is to declare the functions outside the component and then dynamically import the package in a `useEffect`,...

When styled components are declared at the top of a file, this can be quite frustrating as highlighting for all code below it are broken

> try toast.* instead of toast() `toast.message()` exhibits the same behaviour as the described bug - the loading spinner remains and the state persists.