Its javascript to typescript, which unless I'm missing something, can be done with `mv foo.js foo.ts`. No examples of any transforms done by the tool.
And it wasn't one sentence, it was a sequence of questions and answers.
I guess they started with the title for the blog post and didn't really worry about showing whether it did anything useful or not.
How would you verify that the ported code actually works if you don't port the tests and examples?
I see tremendous use in a tool that could be used to port "any" library to any language. I'm very skeptical if this works if the library itself depends on other language specific libraries, ... but we'll see.
If you'd seriously want to use that port in production it only makes sense to port the tests and examples. How would you verify the ported code works otherwise? This also means that if the original library has bad test coverage.. you have too.
Port tests, run them against unported code. Port code, run it against unported tests? That way you also verify that the public api hasn't changed