Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[RFC] Move to Typescript
See original GitHub issueWith more OS projects now planning to move to Typescript (jest, Vue.js, etc.), I think it would be time to think about doing the same. Typescript has matured and now with eslint and babel both supporting Typescript as well, it should be future proof.
Additionally, I think the tooling around Typescript (speed, autocompletion), etc. is far head of flow currently.
I would start with “rewriting” smaller packages (like css-functions and theming) in the beginning.
Also, I started writing the new docs with Typescript.
Are you willing to implement it? Yes
EDIT: I started rewriting the core in my fork in Typescript as an experiment.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:24
- Comments:89 (79 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Another option I discovered today, also used by preact https://www.typescriptlang.org/docs/handbook/type-checking-javascript-files.html
Checking types using jsdoc types using ts compiler.
I would prefer it if we did an incremental switch to typescript. I think the developer experience is far inferior to Flow and we might even see more engagement from the community in terms of PRs.