Allow for non-fixed version of @testing-library/dom
See original GitHub issueHi, thanks for this package, it’s pretty awesome 👀 🎉
I was wondering if the package.json
could be updated to have a semver range for the @testing-library/dom
dependency, rather than a fixed version: https://github.com/testing-library/user-event/blob/master/package.json#L56
Suggestion:
- "@testing-library/dom": "5.1.1"
+ "@testing-library/dom": "^5.1.1"
This way I don’t have to have multiple versions of @testing-library/dom
installed, and you don’t have to constantly update the version in your package.json
😄
Happy to submit a PR if you want
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
@testing-library/dom - npm
Simple and complete DOM testing utilities that encourage good testing practices.. Latest version: 8.19.0, last published: 2 months ago.
Read more >How to use the @testing-library/dom.fireEvent.focus function ...
Secure your code as it's written. Use Snyk Code to scan source code in minutes - no build needed - and fix issues...
Read more >Ask Question - Stack Overflow
It seems that the latest update from @testing-library/dom (8.18.0) is creating the error with cypress and remix. You should revert back to ...
Read more >@testing-library/dom | Yarn - Package Manager
Important: This documentation covers modern versions of Yarn. For 1.x docs, see classic.yarnpkg.com. Yarn.
Read more >Install | Testing Library
npm install --save-dev @testing-library/dom ... The main file is configured to compile down to support the version of node that is ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think that would make a lot of sense.
🎉 This issue has been resolved in version 4.2.0 🎉
The release is available on:
Your semantic-release bot 📦🚀