[FR] Support Typescript

[John0x]

I believe that TypeScript support for both the admin panel and the API would be a great addition. Adding typescript support for the admin panel shouldn't be too much of a problem, since you're already using webpack for bundling, right?

[Aurelsicoko]

We are also thinking about using Flow... We will certainly make a survey to ensure the community is following us on this choice. We want to make sure everyone could contribute easily to the project like it's already the case.

@John0x Can you make a feature proposal on the community vote page? I'm closing the issue because it's not really an issue but more like a feature request.

[John0x]

@Aurelsicoko I'd be willing to take care of most of the typescript integration, if you would guarantee, that it will be merged.

I'll post it on the vote page.

[Aurelsicoko]

@John0x It could be awesome 👍

[oeddyo]

where's the vote? I'd love to vote for ts :D

+1

[erikvullings]

Unfortunately, there is still no option to vote for this feature. In the mean time, I've created a simple CLI, strapi-to-typescript, to generate typescript interfaces from the api/models/**.settings.json files.

npm i -g strapi-to-typescript
sts [PATH\TO\STRAPI\API\FOLDER]

[TimMensch]

TypeScript is a best practice on Node today. I came to look for options for Loopback, and will be ignoring Strapi as a legacy project without TypeScript support.

There's no vote option, there's no mention of TypeScript anywhere, and there's no @types/strapi module. That pretty much kills Strapi as an option.

[derrickmehaffy]

@TimMensch Your always welcome to develop it yourself and create a PR!

Strapi is an open source project and their team is quite small, naturally the community is what helps make a project!

Always have to think on the positive side :)

[NickBolles]

I would also contribute a lot to the typescript implementation.

I think that having defined classes, interfaces and types for Services/Controllers/ORMs etc would be extremely beneficial to Strapi.

@John0x @erikvullings @TimMensch have any of you made any progress on this? Should we get something going?

Maybe we start with a small part and get the tooling in place and do things one by one

[TimMensch]

@NickBolles I was serious when I said I would be ignoring strapi. My comment above resulted in excuses and a request for someone else to do all the work -- which is non-trivial and would require the cooperation of the project.

And then I get more downvotes than upvotes, so this community clearly hasn't gotten the memo that TypeScript is where we all should be. As I said, it's a best practice today. Anyone who ignores that fact is going to fall behind, "small team" or no.

It's beyond just creating declarations, too. You'd need to create a generator for TypeScript signatures for each model. I've done this before, but I don't really feel the need to join a community that's borderline hostile to TypeScript. Too much chance for conflict.

Loopback 2 will be 100% TypeScript (required! not optional! They got the memo.); until Loopback 2 is release-quality, I'm using FeathersJS+Feathers-Sequelize+Sequelize-Typescript+Feathers-Swagger. Not perfect, but much better than trying to cobble together TypeScript support for a community that doesn't care.

If your project is risk-tolerant enough, you can use Loopback 2 today with full TypeScript support; they stilled called it "alpha" when I looked last, and my enterprise client wouldn't have been happy using an "alpha" quality product.

[abdonrd]

I think TypeScript could be a good thing. 🙂