...And this kata is not about performance.

1.0 has been enabled so I am goingto reject the forks

Needs fixes for method accessor - methods that are merely accessed but not called should not be saved into the history array.

merged to node v18 and approved

I discussed this with some mods, and the resulting opinion is that this is not a great idea. I like the motivation behind it, however it adds a fair bit of complexity which:

1. Makes the solver experience a bit worse (longer submit times)
2. Makes translating/updating existing langs to be consistent, a lot harder and more work
3. Users can pretty easily just get around it in most langs (eg. sleep in Python)

So I am gonna reject this, sorry.

Try poking around the runtime environment.

The sample tests are just the template, there should be actual sample tests.

Please use spoiler flag next time.

I think a chance for Math.random() to be 0 is exceptionally rare though (maybe 1 in a billion) but changed it to your suggestion nonetheless. I also make the test cases more semantic and more conforming to the ES6 standard.

It is theoretically possible for Math.random to return 0. ( I did some checking, and I have yet to see it do so, but it is documented it might happen. )

let len = Math.ceil(Math.random() * 30); should be let len = Math.floor(Math.random() * 30) + 1;

In CW JS, the test suite is in a closure that is wholly, completely, absolutely inaccessible to user code ( in other languages, this may be different ). There is no need for names like gen_fcw34gvw34gw, they only distract.

I changed back to the original author's solution with 2 space indents.