Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support TypeScript for React components #12696

Merged
merged 2 commits into from
Mar 12, 2020
Merged

Conversation

turt2live
Copy link
Member

@turt2live turt2live merged commit 296e701 into develop Mar 12, 2020
Web App Team automation moved this from In Review to In Test Mar 12, 2020
@turt2live turt2live deleted the travis/typescript-2 branch March 12, 2020 00:36
@@ -94,7 +94,7 @@
"@babel/preset-typescript": "^7.7.4",
"@babel/register": "^7.7.4",
"@babel/runtime": "^7.7.6",
"@types/react": "^16.9.17",
"@types/react": "16.9",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this no longer a caret dependency (also on matrix-org/matrix-react-sdk#4203)?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

because yarn is awful for two reasons: it doesn't default to caret when installing things, and we should be pinning our types to our react version. 16.9 still gets resolved the same as 16.9.x, which is compatible with carets.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So 16.9, ^16.9 ^16.9.0 all get resolved differently? Also, if this is the correct treatment for @types/react, should @types/react-dom below also be updated?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants