Migrate project to TypeScript #86
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Awesome that you started it! 🤩 Let's pick a moment (after my holidays) and merge this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚨 Please review the guidelines for contributing to this repository.
Hi @ramgrandhi, peeps,
I've taken a bit of time to migrate this project to TypeScript. What's added is I've migrated all the files to TypeScript (shallowly for now).
The project does build and the tests do run. I have configured both eslint and jest to work with typescript as well.
One thing that remains is that we need to figure out how to build it before we publish it of course.
*.spec.js)🙌 Thank you!