Closed YangChen0930 closed 9 months ago
I also encountered the same problem
I reverted to v0.15.5, fixed this problem tentatively.
Ok, I've released v0.15.7
to npm which should fix this problem. Please give it a try when you get a chance.
Thanks, this change fixed the issue for us.
This error occurs with the new version