You are abosolutely correct,sir.My brain was about to explode after sorting

Not a big deal as long as edge cases for same total sales are tested

Your code does not comply to below

Note: if multiple products have the same revenue, order them according to their original positions in the input list.

Nope, that is the assertion messages, whereby the LHS array indicates your output whilst the RHS indicates the correct one (expected).

Not a kata issue though, your code does not comply to below

Note: if multiple products have the same revenue, order them according to their original positions in the input list.

Not a kata issue, your code does not comply to below

Note: if multiple products have the same revenue, order them according to their original positions in the input list.

Not a kata issue, your code does not comply to below

Note: if multiple products have the same revenue, order them according to their original positions in the input list.

Good Kata, nice work! I think updating the Node version would be a good idea. The JS sort method has been stable since 2019 and that should be reflected in the Kata.

Ruby translation kumited:

https://www.codewars.com/kumite/5e6a5366f43e260015dbf842?sel=5e6a5366f43e260015dbf842

I think sorting is too costly for this problem. Am I wrong?

No reason behind. But Javascript does have a Issue with the sorting algorithm if revenue is the same. so we included it into the Testcases.