maxjhandsome
/
react
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
react/fixtures/dom
History
Ming Ye 5940934967
Update to Jest 29 (#26088) 
## Summary

- yarn.lock diff +-6249, **small pr**
- use jest-environment-jsdom by default
- uncaught error from jsdom is an error object instead of strings
- abortSignal.reason is read-only in jsdom and node,
https://developer.mozilla.org/en-US/docs/Web/API/AbortSignal/reason

## How did you test this change?

ci green

---------

Co-authored-by: Sebastian Silbermann <silbermann.sebastian@gmail.com>
 		2023-02-09 17:07:49 +01:00
..
public Upgrade prettier (#26081) 2023-01-31 08:25:05 -05:00
src Update to Jest 29 (#26088) 2023-02-09 17:07:49 +01:00
.gitignore `act()` - s / flushPassiveEffects / Scheduler.unstable_flushWithoutYielding (#15591) 2019-05-16 17:12:36 +01:00
README.md reference yarn instead of npm in dom fixtures README (#11374) 2017-10-26 17:51:58 +01:00
package.json Update to Jest 29 (#26088) 2023-02-09 17:07:49 +01:00
yarn.lock Update to Jest 29 (#26088) 2023-02-09 17:07:49 +01:00

README.md

DOM Fixtures

A set of DOM test cases for quickly identifying browser issues.

Setup

To reference a local build of React, first run yarn build at the root of the React project. Then:

cd fixtures/dom
yarn
yarn start

The start command runs a script that copies over the local build of react into the public directory.