Begin TypeScript Migration?

Summary description

Migrate project to TypeScript.

Implementation

Looks like an easy win as TS can be adopted incrementally. To add support in this project simply:

yarn add --dev typescript && touch tsconfig.json && dc down && dc up -d

Next.js will populate the tsconfig.json file with some sane defaults as the container comes up and you can start renaming source files to end with ts and tsx. (Note at least one TypeScript file is required in the project before the tsconfig.json file will be autopopulated with defaults.)

Step two would be to get rid of the prop-types dependency. If all goes well, start porting other parts of the framework. Consider pairing this work with #643.

Motivation

Type safety. IntelliSense. Better static code analysis resuling in fewer regressions.

Notes

Doesn't seem to work on the v3.1.0 tag but worked for me on trunk. Probably a Next.js update which allows the tsconfig.json file to auto-generate.

[janus-reith]

Incremental Migration to Typescript indeed is really simple with nextjs.
However, I think this is a general decision that needs to be made across the stack.
On the api, migration to typescript could come with other benefits and help generalizing schemas.

[rc-publisher]

🎉 This issue has been resolved in version 4.1.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀