Uh oh!
There was an error while loading. Please reload this page.
fix: add fork-ts-plugin as a dependency - #6401
Conversation
previously referenced but not dependent. closes#6400
facebook-github-bot
commented
Feb 11, 2019
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! |
ghost
commented
Feb 11, 2019
I think this is a bad idea. I don't use TS, why should I install this plugin? |
facebook-github-bot
commented
Feb 11, 2019
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
elevatebart
commented
Feb 11, 2019
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 |
elevatebart
commented
Feb 11, 2019
That was my reflex too. Hope someone checks here soon. |
deftomat
commented
Feb 11, 2019
My apologies guys. That's the "classic" monorepo issue. I forgot to add it into dependencies. 😞 |
deftomat
commented
Feb 11, 2019
Looks like #6395 is a better approach. |
ianschmitz
commented
Feb 11, 2019
Hey just looking into this now. |
elevatebart
commented
Feb 11, 2019
It still adds the ts-checker dependency to people without typescript... Oh well... |
ianschmitz
commented
Feb 11, 2019
We decided to revert #5903 to fix 2.1.5 is now available |
previously referenced but not dependent.
closes#6400