Vitaly

> I think this PR scope should be reduced to handle default formatting options, and open a new PR for patching indent. Can I remove handling default formatting options here...

@RyanZim but what do you think about TS migration? Are familiar with `tsc`? By using it we can generate both cjs and esm from one codebase (I hope it'd work...

> AppVeyor config I'm just not aware of it. Does it duplicate the GitHub's integration?

Hmm... this article is insane. However `.ts` files still have better syntax. Here is more comprehensive response: > nobody likes wasting time compiling stuff. Everybody knows how slow TSC is...

Agree, didn't notice how long that post was 😆

So, finally got moved to https://github.com/jimmywarting/you-might-not-need-typescript/discussions/3

diamond-square and flying-squid will definitely benefit from it: https://github.com/PrismarineJS/diamond-square/pull/15/ (so we don't have to open another pr in future for the short_grass rename)

> Why would that benefit? Because I can use simple function like `getMcData.getRenamedData('blocks', 'tall_grass', '1.17.1', version)`. And that's it. I do not need to care of anything else. With features...

So I don't see any benefits of not using it. Also we can make things even simpler with something like this: ```ts const mcData = require('minecraft-data') const targetVersion = '1.13.1'...

> If there are changes between versions they need to be correctly handled properly, not like that I'm not saying that you shouldn't not use features at all. But in...