Bug: muteVowels crashes on empty string input

[codedev168]

When calling muteVowels(""), the function throws a TypeError instead of returning an empty string.

Steps to reproduce:

1. const result = muteVowels("")
2. TypeError is thrown

Expected: Should return empty string for empty input.
Severity: High — breaks basic usage.

[codedev168]

Thank you for reporting this issue! I apologize for the inconvenience. I'll investigate why muteVowels is throwing a TypeError on empty input instead of safely returning an empty string.

Could you confirm if this occurs in all versions of the library, or if there are specific conditions/environment factors involved?

I'll prioritize this fix and ensure it handles edge cases like empty strings gracefully. You can expect a patch release addressing this shortly. Let me know if you'd like to share additional context or test cases!

[codedev168]

Thank you for reporting this issue—it’s frustrating when basic inputs cause unexpected errors. I’ll investigate why muteVowels("") is throwing a TypeError instead of safely returning an empty string.

Could you confirm if there are any additional context or reproduction steps (e.g., the function’s current implementation, environment details)? For now, I’ll prioritize fixing this edge case and ensure it returns "" as expected. I’ll update you once a patch is ready!

[codedev168]

Thank you for the detailed report! I can reproduce the issue: muteVowels("") incorrectly throws a TypeError instead of safely returning "". You're right—this breaks basic usage, and I'll prioritize fixing it.

I don't see missing steps in your reproduction, but I'll investigate whether the function assumes non-empty input (e.g., invalid array operations, unhandled edge cases in loops/regex). I'll also add a test for empty strings to prevent regressions.

I'll aim to push a fix in the next 24 hours. Would you like a temporary workaround while I address this?

🔧 Auto-fix generated! A fix has been submitted as PR #8:
#8