Yeah, this was definitely a problem in version 3.40.2, which was brought to my attention by some helpful users on GitHub. :) Thanks for reporting it too!

Version 3.40.3 should fix this.

And thank you very much for the review!