Skip to content

Tags: ReactDOM/react-testing-library

Tags

v5.8.0

Toggle v5.8.0's commit message
feat: testHook returns result ref object (testing-library#297)

v5.7.0

Toggle v5.7.0's commit message
feat: wrapper for testHook (testing-library#296)

* feat: wrapper for testHook

* Ignore eslint rule

v5.6.1

Toggle v5.6.1's commit message
fix(TS): typing of testHook (testing-library#292)

* Adds typing for testHook return

* Adds typings section to contributing.md

v5.6.0

Toggle v5.6.0's commit message
feat(testHook): modify testHook to return unmount function (testing-l…

…ibrary#290)

* Returns unmount function on testHook

* Adds test for unmount function; Adds example of useEffect

* Add Andrewmat as contributor

* Adds rerender on testHook return

v5.5.4

Toggle v5.5.4's commit message
fix: act polyfill for React 15.x (testing-library#288)

Fixes testing-library#287

v5.5.3

Toggle v5.5.3's commit message
fix(act): add a polyfill

Thanks @threepointone!

v5.5.2

Toggle v5.5.2's commit message
fix(build): upgrade all deps

Closes testing-library#279

v5.5.1

Toggle v5.5.1's commit message
fix: declare "module" field in package.json (testing-library#282)

**What**:

This change exposes the ESM version of the build, in the same fashion that the ES modules build is declared in `dom-testing-library`.

**Why**:

The ESM build is currently generated and distributed upon publish, though it is not exposed via `package.json`. My admittedly selfish use case for this is in having better heuristics around some linting rules (namely `import/named`).

**How**:
• Added the `module` field to `package.json`, pointing it at the path of the built artifact

**Checklist**:

- [ ] Documentation (N/A)
- [ ] Tests (N/A)
- [x] Ready to be merged
- [x] Added myself to contributors table

**&c.**:

Thanks for this library–it's great! Let me know if there's anything I overlooked or you would like to see changed.

v5.5.0

Toggle v5.5.0's commit message
test: fix test coverage and testHook tests

Sorry @donavon, this is the best we can do I think :-(

v5.4.4

Toggle v5.4.4's commit message
fix(TS): add explicit annotation to Query type (testing-library#260)

<!--
Thanks for your interest in the project. Bugs filed and PRs submitted are appreciated!

Please make sure that you are familiar with and follow the Code of Conduct for
this project (found in the CODE_OF_CONDUCT.md file).

Also, please make sure you're familiar with and follow the instructions in the
contributing guidelines (found in the CONTRIBUTING.md file).

If you're new to contributing to open source projects, you might find this free
video course helpful: http://kcd.im/pull-request

Please fill out the information below to expedite the review and (hopefully)
merge of your pull request!
-->

<!-- What changes are being made? (What feature/bug is being fixed here?) -->

**What**: Bug

<!-- Why are these changes necessary? -->

**Why**: The existing typescript definitions fail to compile with `--noImplicitAny` enabled. 

<!-- How were these changes implemented? -->

**How**: I forked the project and tested that the updated declaration compiles correctly.

<!-- Have you done all of these things?  -->

**Checklist**:

<!-- add "N/A" to the end of each line that's irrelevant to your changes -->

<!-- to check an item, place an "x" in the box like so: "- [x] Documentation" -->

- [ ] Documentation N/A
- [ ] Tests N/A
- [X] Ready to be merged
      <!-- In your opinion, is this ready to be merged as soon as it's reviewed? -->
- [ ] Added myself to contributors table 
      <!-- this is optional, see the contributing guidelines for instructions -->

<!-- feel free to add additional comments -->