Quite a pretty nice and challenging kata to figure out.

-42

Not really a suggestion pertaining to this kata, but may be worth making as another kata instead.

This really isn't a problem.
You are making 'i' an int, and the result of sizeof(strings)/sizeof(char*) is an unsigned long
The compiler is just telling you that an int and unsigned long are not identical data types, and to be careful comparing them.

Fixed.

Fixed in this fork: https://www.codewars.com/kumite/628a6f42443a3a0027214190?sel=628a6f42443a3a0027214190

changed to 'maze'

fixed

I know the code will still work, that's why I tagged this as a suggestion and not an issue.

I'm very new to JS, so maybe I'm not used to seeing a variable with the same name as commonly used functions and/or data structures. But in my experience in other languages, this is not best practice.

there's no problem with the .map method which is tied to the Array namespace; i guess the ambiguity is with Map

This is not a proper way to raise an issue. Consecutive spaces don't display properly in markdown, we don't know what you are refering to. If the map argument annoys you, you just can give it another name. However, there is no reason a parameter could not be named map in Javascript, there is no ambiguity possible with Array.prototype.map if that's your idea (however we cannot know since you don't say it). Please read carefully the documentation and try to follow a minimal quality at the time of posting issues if you hope somebody is able to fix them someday: https://docs.codewars.com/training/troubleshooting/

The test cases are a mess!
there's a test on a string " xoxoox " which obviously has a space at it's end so no matter how much the 'x' and 'o' changes the space will not be effected. Eventually the result should be true but the test expects it to be false!
This challenge has another issue which is the name of the argument! it should be something else than 'map' because it can get confusing in some cases.