We released a new version that should fix this issue.

Hello everyone!

We've identified that the issue stemmed from duplicating the same module twice. We have deployed a fix, so you should not experience this problem anymore.

Thank you for reporting this