It's really frustrating, but we're still actively searching for a solution. As soon as we find something, we'll share it here. Are you only experiencing the error locally, or does it also occur when you deploy?"

Hey, did you find any solution? We are having the same problem.