Migrate from CoffeeScript to TypeScript

[smorimoto]

CoffeeScript is already a little obsoleted. Does the core development team interested in migrating to TypeScript or JavaScript and/or improving React performance? (*This is a question. Not an issue.)

[cl8n]

new components are already being written in typescript and I assume that means all of the coffeescript will eventually be replaced too

[smorimoto]

Yes, I knew that, so I wondered. Also some TypeScript codes are obsolete and should be checked by ESLint. I can set it up, So I can create PR. For example, it's better to use "type" instead of "interface". (Except for some complicated packages.)

[smorimoto]

*As far as I remember, TSLint will be deprecated later this year.

[LiquidPL]

There's a lot of code written in CoffeeScript and I'm pretty sure that migrating all of it over would be a major effort.

Also yeah, new components are being done in TypeScript already, so there's a good chance a lot of components will be rewritten anyway as we rework them.

[smorimoto]

It over would be a major effort.

I really think so. I just switched to ESLint and there are about 600 errors.

[smorimoto]

I think it's enough if you do the migrate when you need it.

[peppy]

You're more than welcome to help with this, but it is (as you can understand) a very low priority.

[smorimoto]

I get it! I will try it when I have much time!

[notbakaneko]

Moving to typescript is the eventual goal and we'd be glad to accept contributions in migrating the existing coffeescript to typescript. We'd also accept contributions for better test coverage and typings for existing coffeescript modules to help in migrating to typescript.

[LiquidPL]

I don't think there's a reason to close this one though.

[smorimoto]

I opened this as a question and so I close this. but I reopened because this included in milestone.

[taylankasap]

This should be mentioned in CONTRIBUTING.md since it also mentions a similar thing (moving from Laravel Blades to React).