fbb5d48283
There is a breaking in change in the `MatcherContext` that is passed to
matcher functions, so we now have `!!this.isNot` in a few places. The
same could happen to custom matcher in the wild.
```ts
// Old
{
isNot: boolean;
promise: string;
}
```
```ts
// New
{
isNot?: boolean;
promise?: string;
}
```
Fixes #23612.
16 lines
486 B
JSON
16 lines
486 B
JSON
{
|
|
"name": "expect-bundle",
|
|
"version": "0.0.1",
|
|
"private": true,
|
|
"scripts": {
|
|
"esbuild": "esbuild ./src/expectBundleImpl.ts --bundle --outdir=../../lib/common --format=cjs --platform=node --target=ES2019",
|
|
"build": "npm run esbuild -- --minify",
|
|
"watch": "npm run esbuild -- --watch --sourcemap",
|
|
"generate-license": "node ../../../../utils/generate_third_party_notice.js"
|
|
},
|
|
"dependencies": {
|
|
"expect": "29.5.0",
|
|
"jest-matcher-utils": "29.5.0"
|
|
}
|
|
}
|