Create a list of kata which cannot/should not be updated to Node 18 #223

hobovsky · 2025-02-05T08:36:41Z

There can be a couple of reasons why a kata should not, or cannot, be updated to Node 18:

There are new features in Node 18 not present in Node 8 (or whatever is the current version of the kata), and updating it to Node 18 will make the kata trivial or severely misranked,
The kata is based on some internal behavior of the runtime which changed,
The JavaScript translation of the kata is already bad for some reason, and updating it to Node 18 would be a lot of unnecessary effort,
... maybe some other reasons I cannot think of right now.

Ideally such kata would be handled by removing or disabling the JavaScript translation, but since this feature is not there yet, all we can do is to collect them and save the list for the future.

Please drop your proposals of kata which should not be updated to Node 18, with a short explanation. You can also add some updated kata which you think should have their JS translation removed. if you find any. I will collect the suggestions into some list, somewhere, for future reference when we will be finally able to remove approved translations.

flatten() - can be solved with a built-in in Node 18 (and even now it can be almost trivially solved with Lodash).
Sum Strings as Numbers - becomes trivial with native bigint.