yep, my first ones were already hidden.
current one would not work for the 3kyu kata anyway

ok, I'll post another.

it seems that kata needs a JS translation as well ;-)

couldn't find a chat/thread there with that discussion.
but you could ping me ( @twilight_sun ) if that makes sense. I have no certain opinion at the moment

done (submitted the solution). maybe not the clearest code, but should be faster

oh, excuse me =)

It depends on what ranges are ok for your solution, as mine is a result of looking at numbers without understanding of a problem per se

now it works, thanks!
btw, input range looks easy, it could work for much bigger numbers with a little modification ;)

It seems there is a typo in "Simple tests" (in "Basic tests"):

for (let i = 0; i < allFlav; i++)

should be

for (let i = 0; i < allFlav.length; i++)

I've also thought there could be at least 2 kata:

1. easy: this one but without 'wrong' sales
2. harder: one would need to output a result for every sale; or with some 'wrong' sales, etc

P.S. as this is quite a practical task (but not in SQL) I know there exists several approaches to calculating a gross margin; not only different ways of dealing with sales of skus that are not in stock but also a different algos, not only FIFO.

Notes says:

It is not possible for more units of a certain product to be sold than purchased at any given moment in time because the FIFO Gross Margin calculation assumes that sales are matched to prior purchases.

but in example tests I see

edge_case_purchase_data = [
  # sales exceeding purchases: only 2 units purchased, but 3 units sold
  {sku: 'exceed_001', purchase_date: '2023-01-01 10:00', price: 10.00, qty: 2},
...
edge_case_sales_data = [
  # sales exceeding purchases: 3 units sold, but only 2 units purchased
  {sku: 'exceed_001', sale_date: '2023-01-05 10:00', price: 20.00, qty: 3},

it looks like a contradiction to me. So from the description the result for this sku is unclear (could be 20, 30 or even 40)