Ondřej Žára

> For docs, my experience with TypeDoc has been that it unfortunately doesn't have great support for richer documentation that includes interactive elements, usage samples in context, etc. I am...

> I'd _highly_ recommend taking a look at the [Jest docs](https://jestjs.io/en/) and some examples: it supports Jasmine's API for test groups, assertions, etc., so (picking an file from the specs...

@lostfictions I just ported `ROT.Display` and boy, that TS is a lot of work! You certainly did quite a lot of work in your TS fork. Kudos to you! (I...

Thanks for all the comments. I decided to stick with `([] as string[]).concat`, although in my opinion it makes the code much less readable. I consider `[].concat(x)` as an idiomatic...

> The output is always a single `.d.ts` file, and Typescript handles this for you. The first step is just to set `"declaration": "true"` in your `tsconfig.json`, and then point...

Slowly moving forwards. - Build process (Makefile-based) almost complete and documented:  - More modules ported (utils, color, stringgenerator) - Autogenerated docs - Manual semi-ported

I am almost done with the refactor. Some remarks before the work is completely finished: - there is no separate *node* version of rot.js; the library simply contains Node support...

I suppose the problem here is that there is no well-defined use case for these values. They are used as sane defaults in several places, where map size is optional....

Done. The TS codebase has been merged into master. The *TS* part is now finished, but the *modernizing* is not: we have Classes and let/const statements, but the code still...

Hi @myevan , thanks for the report! It would be great if you managed to send a PR, provided you were already able to fix the issue.