Converting to TypeScript #2989
Replies: 2 comments
-
Awesome notes, especially with the electron resources! :) I did a brief proof-of-concept during some downtime as well, primarily using https://skovhus.github.io/blog/flow-to-typescript-migration/ and https://blog.logrocket.com/setting-up-a-monorepo-with-lerna-for-a-typescript-project-b6a81fe8e4f8/. Instead of the You're right though, it's a pretty big undertaking, somewhat manual (since there are some repetitive changes for each package & plugin), but with the ts compiler and ES Lint it is certainly achievable. We've also talked about this internally for a while now, and one of the items on the roadmap was to introduce some degree of E2E smoke tests before any major refactors, which are now in place ( |
Beta Was this translation helpful? Give feedback.
-
We've moved to TypeScript! 🎉As of 2021.4.0, the repository is (mostly) on TypeScript. Here was the plan of attack: #3654 There's still a bit more to do, so don't hesitate to keep cleaning it up as you work on other issues. Great work by the team so far and we're excited to push this for our community ❤️ |
Beta Was this translation helpful? Give feedback.
-
I've started a converting this repository from Flow to Typescript, but there is quite a lot of things that pose a challenge and honestly, I'm not sure whether or not it's even worth it at this point based on the initial start. 😅
Right now I have at least somewhat converted the
insomnia-app
package to TypeScript, however, there is quite a bit of work still left:Record<string, any>
scripts
andapp
structure tosrc/*
structure to create consistency@types
for librariesThe above must be done for each package.
Resources that I have been leveraging for guidance around monorepos and typescript:
There is also the resource for electron:
Beta Was this translation helpful? Give feedback.
All reactions