Slap the module author(s) on the wrist. Lexically disabling warnings will work under -w and of course you can localize $^W as we used to do. So I don't see any excuse not to take the proper action to disable them as needed if you're intentionally doing something that may raise warnings. My take on this is fairly rigid. There are times that call for not complying with warnings or strict, but you should at least have the decency not to force that choice unto whoever is using your code as well.

File a bug report or complain to the author by email.

Makeshifts last the longest.