-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
fix: add fork-ts-plugin as a dependency #6401
Conversation
previously referenced but not dependent. closes #6400
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed. If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
I think this is a bad idea. I don't use TS, why should I install this plugin? |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
Hey @demkovych, I see your point. |
@elevatebart I don't know. As i see, we can't use |
The problem of the dependency issue will still occur if someone is using typescript, without having this plugin as an explicit dependency, react-dev-utils will break again. This eslint rule would have caught this issue |
Or rollback to |
That was my reflex too. Hope someone checks here soon. |
My apologies guys. That's the "classic" monorepo issue. I forgot to add it into dependencies. 😞 |
Looks like #6395 is a better approach. |
Hey just looking into this now. |
It still adds the ts-checker dependency to people without typescript... Oh well... |
We decided to revert #5903 to fix 2.1.5 is now available |
previously referenced but not dependent.
closes #6400