Simen Bekkhus comments

Results 1232 comments of


                                            Simen Bekkhus

fix: stop printing the same error for each individual test caused by beforeAll when it fails

CI is failing - would you be able to take a look? Or is that waiting for https://github.com/facebook/jest/pull/13273#issuecomment-1250138230?

[Feature]: Support loading jest.config.ts as ESM

https://github.com/jestjs/jest/releases/tag/v30.0.0-alpha.3 for `.cts` support

fix(jest-leak-detector): gc() even harder

FWIW, GC run was made more aggressive in #14526

test.each /describe.each dont wait for beforeAll to finish

See https://jestjs.io/docs/troubleshooting#defining-tests. Jest has never supported defining tests asynchronously. One alternative would be for you to use native ESM and top level await. ```js const data = await fetchSomeData(); test.each(data)``;...

Re-export config-plugins from expo package and update docs

Official plugins also use it. https://github.com/expo/config-plugins/blob/ed020d236b8fa4a810adf90a9773d9a2fba36fd4/packages/react-native-pdf/src/withPdf.ts#L7 Maybe expose it as `unstable` or something up until a replacement is made?

Add more data to promise matchers

@harelmo I like these changes! could you rebase and fix CI?

Add toIncludeAllMembersInOrder.

@sandinmyjoints could you resolve the conflict?

Request: option to let `no-duplicates` force type & normal imports to be de-duplicated

I'd assume somebody picking up #2229 would be welcome, so I suggest starting there 🙂

feat: enable Corepack (pnpm support, unbundle yarn)

Running `corepack enable` and installing yarn should be equivalent to what we have today, right? Except for `pnpm` command becoming available. Seems like an improvement on the current situation, plus...

feat: enable Corepack (pnpm support, unbundle yarn)

We should wait for whatever the resolution in https://github.com/nodejs/node/issues/51931 and https://github.com/nodejs/node/pull/51886 is https://github.com/nodejs/TSC/issues/1518