OP solved it, closing

just creating that sod sieve times out already, is micro optimisation required?

duplicate of this issue

this app use node 8.1.3 which doesn't support private methods(
you should use another approach for this purpose

If that doesn't answer the question, nothing does.

Hi, I was having the same problem as you. Until I realized that the arguments that you are supposed to call the functions with, should not be passed in like this: theFunction([argument1, argument2, argument3]).

The functions should be called like this: theFunction(argument1, argument2, argument3).

-Note: make sure you call the functions with all the arguments at the same time. If you loop and do one argument at a time it will not work.

Hopfully this helps :)

And how is this an issue?

It's Great feature of Codewars to get surprises after submitting!

I agree, nice kata.

i'm glad you liked it :)

Yea the solution for the other one covers this one.
The only difference I see is that the other one can have leading 0's in the input strings.
I did the other one in PHP and just had to translate my solution to javascript for this one.

Maybe something here will be helpful?

It may be because you are not dynamically allocating memory for the return value.

The translation was written with the exact (correct) tests created by the author, including tester("NWN", 60); in both the sample and fixed tests. This has not changed. I can see no reason why you think the intger value is 66.