Skip to content

Create @testing-library scope for publishing. #260

Closed
@kentcdodds

Description

@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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions