-
-
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
chore: Allow to install eslint-plugin-react ^7.1.0 to get rid of warnings on start #3087
Conversation
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! |
What warnings are you talking about; could you please give me more context? These are development dependencies of a required package, so they should never be installed under normal use anyway. |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
So, when you start the app, you get the warnings reported in my first post. The problem is that If you loosen the requirement here, the latest version will be installed and used by all the other packages of create-react-app as well.
If I put this in my package.json:
The warnings go away |
I guess more appropriately, I cannot reproduce this. Are you using Yarn, npm? What version? What Once again, you're modifying a development dependency which should not affect the install tree (ever); did you mean to edit the package in |
Oh, yeah you are right, I should have edited the one in The warnings comes out after you eject and thinker a bit with the app, but the base problem is that react-scripts requires an older version without any particular reason. |
I do not see us loosening this requirement as it's not clear to me how this benefits anything and how it couldn't be simply overridden when you eject (or how it causes this problem). If there's a problem here, it sounds like it's more in-line with invalid configuration or a breaking change released under a non-major version (and then stemming from configuration in |
Can't we bump it to |
I would like to figure out the underlying cause before we update packages. |
I had similar issue. adding
to my But i didn't get this warring while starting server via |
Hello! I'm a bot that helps facilitate testing pull requests. Your pull request (commit d68fa77) has been released on npm for testing purposes. npm i react-scripts-dangerous@1.0.14-d68fa77.0
# or
yarn add react-scripts-dangerous@1.0.14-d68fa77.0
# or
create-react-app --scripts-version=react-scripts-dangerous@1.0.14-d68fa77.0 folder/ Note that the package has not been reviewed or vetted by the maintainers. Only install it at your own risk! Thanks for your contribution! |
We will bump this plugin in the next major. It's not supported to install and use arbitrary versions of ESLint plugins in a non-ejected project. |
This should allow people to install eslint-plugin-react 7.2.0 which gets rid of the following warnings when you run
yarn start
: