Create @testing-library scope for publishing.

[kentcdodds]

As brought up by @brentvatne: https://twitter.com/notbrent/status/1130517657546043394 and suggested by @vincentriemer

Basically:

- yarn add react-testing-library
+ yarn add @testing-library/react

I think that I would still refer to it in writing/speaking as "react testing library."

I think it's a good idea and I grabbed https://npm.im/~testing-library so we should be good to start doing this.

I just want to hear what folks have to say.

Here's how I think we should do it:

1. Each package maintainer gets to choose whether they want to be publishing their package under the scope and what version to publish at first.
2. I think I'd like to publish the ones I'm primarily responsible for as 1.0.0 on that scope.
3. Publish a new major version of each package that has moved which is immediately deprecated with a message indicating people should migrate to the new scoped package.

What thoughts do you all have?

[timdeschryver]

Sounds good to me!

[bcarroll22]

I love it 👍

[alexkrolick]

Sounds good to me

[bcarroll22]

I think I'd like to publish the ones I'm primarily responsible for as 1.0.0 on that scope.

I'm curious, for my own decision process, what makes you want to do it this way?

[gnapse]

Sounds great! Would like to have your comments on how it went with your packages, and how to proceed with re-publishing ours. I'm not too familiar with making this change.

[kentcdodds]

I'm planning on doing this today and I will probably livestream it.

[kentcdodds]

Here it is: https://www.youtube.com/watch?v=BN5ELGSV25Q

[kentcdodds]

Do we want to rename the repos?

For example: https://github.com/testing-library/dom-testing-library -> https://github.com/testing-library/dom

[bcarroll22]

👍 I'm good either way

[kentcdodds]

Let's leave it as-is for now and change it later if we decide it makes more sense later :)

[kentcdodds]

After further investigation I've decided it'd be better to continue with the current versioning scheme because the GitHub releases page (and git tags).