-
Notifications
You must be signed in to change notification settings - Fork 470
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
Create @testing-library scope for publishing. #260
Comments
Sounds good to me! |
I love it 👍 |
Sounds good to me |
I'm curious, for my own decision process, what makes you want to do it this way? |
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. |
I'm planning on doing this today and I will probably livestream it. |
Here it is: https://www.youtube.com/watch?v=BN5ELGSV25Q |
Do we want to rename the repos? For example: https://github.com/testing-library/dom-testing-library -> https://github.com/testing-library/dom |
👍 I'm good either way |
Let's leave it as-is for now and change it later if we decide it makes more sense later :) |
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). |
There was an issue with a major release, so this manual-releases.md change is to release a new major version. Reference: #260 BREAKING CHANGE: You must switch from `dom-testing-library` to `@testing-library/dom`
Reference: testing-library/dom-testing-library#260 BREAKING CHANGE: You must update all imports from 'react-testing-library' to '@testing-library/react'
Ok, dom-testing-library and react-testing-library are done. Going to do cypress-testing-library and then I'll be done with this. Who else is planning on moving their packages? cc @testing-library/angular @testing-library/vue @testing-library/user-event @testing-library/core-maintainers @testing-library/jest-dom @testing-library/puppeteer @testing-library/react-native @testing-library/testcafe |
🙋♂ gonna do it real soon with NTL and jest-native |
Reference: testing-library/dom-testing-library#260 BREAKING CHANGE: You need to change your imports from cypress-testing-library to @testing-library/cypress
Ah, actually will we all need permission to publish to the npm organization? |
Yes, you do. Please give me your npm usernames. |
Mine is bcarroll22 |
You're on there already :) |
Make sure you use |
I'm pretty much done with all my stuff. If folks could just give me their npm username then I will get you on the npm org and you should be able to publish. If you'd like a hand, please watch the livestream to see what I did :) |
Oh, and now we have a bunch of stuff in the docs to update 😬 |
I will move the |
react-testing-library has been deprecated in favour of @testing-library/react Relevant issue: testing-library/dom-testing-library#260
I just sent invites to a bunch of the maintainers of various testing-library packages. If I missed anyone let me know! |
react-testing-library has been deprecated in favour of @testing-library/react Relevant issue: testing-library/dom-testing-library#260
Reference: testing-library/dom-testing-library#260 BREAKING CHANGE: You need to uninstall `jest-dom` and install `@testing-library/jest-dom` instead. Then change your imports from `jest-dom` to `@testing-library/jest-dom`.
`jest-dom` has moved to `@testing-library/jest-dom`. Please uninstall jest-dom and install `@testing-library/jest-dom` instead, or use an older version of `jest-dom`. If you do upgrade to `@testing-library/jest-dom`, make sure to update your usage of `jest-dom` to use `@testing-library/jest-dom/extend-expect` rather than simply `jest-dom/extend-expect`. Learn more about this change here: testing-library/dom-testing-library#260 Thanks!
`jest-dom` has moved to `@testing-library/jest-dom`. Please uninstall jest-dom and install `@testing-library/jest-dom` instead, or use an older version of `jest-dom`. If you do upgrade to `@testing-library/jest-dom`, make sure to update your usage of `jest-dom` to use `@testing-library/jest-dom/extend-expect` rather than simply `jest-dom/extend-expect`. Learn more about this change here: testing-library/dom-testing-library#260 Thanks!
`jest-dom` has moved to `@testing-library/jest-dom`. Please uninstall jest-dom and install `@testing-library/jest-dom` instead, or use an older version of `jest-dom`. If you do upgrade to `@testing-library/jest-dom`, make sure to update your usage of `jest-dom` to use `@testing-library/jest-dom/extend-expect` rather than simply `jest-dom/extend-expect`. Learn more about this change here: testing-library/dom-testing-library#260 Thanks!
- jest-dom moved testing-library/dom-testing-library#260 - cleanup-after-each is no longer required https://github.com/testing-library/react-testing-library/blob/master/cleanup-after-each.js
* Update jest.setup requires - jest-dom moved testing-library/dom-testing-library#260 - cleanup-after-each is no longer required https://github.com/testing-library/react-testing-library/blob/master/cleanup-after-each.js * update dependencies
* Update jest.setup requires - jest-dom moved testing-library/dom-testing-library#260 - cleanup-after-each is no longer required https://github.com/testing-library/react-testing-library/blob/master/cleanup-after-each.js * update dependencies
Because get following message when run test: jest-dom has moved to @testing-library/jest-dom. Please uninstall jest-dom and install @testing-library/jest-dom instead, or use an older version of jest-dom. If you do upgrade to @testing-library/jest-dom, make sure to update your usage of jest-dom to use @testing-library/jest-dom/extend-expect rather than simply jest-dom/extend-expect. Learn more about this change here: testing-library/dom-testing-library#260
This package has been replaced with @testing-library/jest-dom as per testing-library/dom-testing-library#260
This package has been replaced with @testing-library/jest-dom as per testing-library/dom-testing-library#260
* fix: rm localUrl api * fix: rm localUrl * chore: migrate testing-library ref testing-library/dom-testing-library#260 * feat: add AppRoute render/component props * chore: rm setupFilesAfterEnv * fix: adjust for cr * fix: adjust JS asset to js asset * fix: rm useless cleanup-after-each * feat: add AppRouteComponentProps ts * chore: update version * fix: interface match to Match
as described at testing-library/dom-testing-library#260
* fix: rm localUrl api * fix: rm localUrl * chore: migrate testing-library ref testing-library/dom-testing-library#260 * feat: add AppRoute render/component props * chore: rm setupFilesAfterEnv * fix: adjust for cr * fix: adjust JS asset to js asset * fix: rm useless cleanup-after-each * feat: add AppRouteComponentProps ts * chore: update version * fix: interface match to Match
Reference: testing-library/dom-testing-library#260 BREAKING CHANGE: You must update all imports from 'react-testing-library' to '@testing-library/react'
As brought up by @brentvatne: https://twitter.com/notbrent/status/1130517657546043394 and suggested by @vincentriemer
Basically:
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:
What thoughts do you all have?
The text was updated successfully, but these errors were encountered: