That's an issue. Reraising as such.

It's good that this errored because this means the tests were using the user's submission solution as the reference solution, which is dangerous

Approved.

Forked and approved

that answer is from way before chatgpt was a thing lol

Ayy, you're the first solver of the kata. Congrats!

I'm glad that you liked it :)

Side note: If you want to try more katas about TS types, you can take a look at this collection I made a couple months ago.

It's bad practice to remove them. It's relying on the tests to include them instead, which leaves these solutions prone to being automatically invalidated in the future if the tests change and their solutions don't compile anymore. The line or two saved by omitting them isn't worth that risk, so you're doing good by keeping them in

I've left TypeScript for a year, and this was my return to form to it after flirting with C++'s metaprogramming instead and oh boy. TypeScript's type manipulation is both lightyears ahead and lightyears behind other languages. This was one of the most frustratingly entertaining exercises on this website, 10/10

approved by someone

Weird extra unnecessary step is expected. Adds nothing to the task.

JS Fork to address this suggestion. Also fixes description, increases documentation, and adds very minor test enhancements