Update documentation to reflect setup when using the CRA version

[gndelia]

Now that this plugin is part of CRA after this PR facebook/create-react-app#8963 we might want to add a mention to it in the docs. Currently, the docs state how to use this plugin standalone, but probably CRA is far popular to ignore it 😛 . Perhaps we could consider

• If I was already using the plugin, what should I do to use the version that comes from CRA?
• If I want to use it as part of CRA, what should I do? Perhaps it's just highlighting which steps could be skipped, or linking to the CRA docs where the steps are mentioned if any.

[Belco90]

Yeah, I have been thinking about it. I even checked other ESLint plugins already included in CRA and they don't mention anything, so not sure what to do.

I guess at least we can add a mention within "Installation" to clarify which major version is included in CRA and since when.

[gndelia]

yeah something simple should be enough, we don't have to go that fancy 😄

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Belco90]

I think we should add this now since CRA uses v4 and we have released v4.

I figured out how to upgrade the plugin to v4 in a CRA project using yarn (with selective dependency resolution), but I don't have any idea how to do this with npm.

Additionally, it would be nice to create a PR to upgrade the plugin in CRA. I think @MichaelDeBoey wanted to give it a try.

[MichaelDeBoey]

Created a PR to add eslint-plugin-testing-library@^4.x to CRA: facebook/create-react-app#10817

[Belco90]

Any ideas about how to suggest updating the plugin to v4 in a CRA project using v3 when dependencies are managed with npm? The only thing I can think of is disabling CRA internal ESLint and reinstall ESLint + plugins directly in the project so the user has full control of it, but I would like to avoid this way.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.