Simen Bekkhus

I just worked with the debugger now while putting together https://github.com/jestjs/jest/pull/14578 - breakpoints in jest sources worked fine. I use `--inspect-brk` and hit `Continue` once the debugger connects, maybe that's...

Ah, within the ts file! That probably needs source maps. I always debug in the chrome dev tools, never within the IDE. So haven't noticed 😅

Awesome! We have some "absolute path to relative path" stuff for stacktraces, and stripping internal frames. That's where I'd assume any issues would arise - beyond that it should be...

One regression: https://github.com/nodejs/cjs-module-lexer/issues/88 In practice, this breaks `jest-watch-typeahead`. Unfortunate that TS types don't have a `default` export of all the things - not sure how to reconcile named exports in...

Fix for the above was to have our own ESM exports, bypassing the lexer entirely: #14661 Released in https://github.com/jestjs/jest/releases/tag/v30.0.0-alpha.1

Multiple runs is the only to make Jest's threshold check work. However, that threshold can be moved out of Jest (to e.g. coveralls or your CI) and then that could...

>I could be mistaken but, wouldn't that still require changes to Jest so that coverage was still collected but not reported? You'd remove `coverageThreshold` from Jest but still collect coverage...

Yeah, this isn't currently possible - see https://github.com/facebook/jest/issues/11453#issuecomment-1040424443. In #12397 we enforce CJS, might be we should tweak this. It's unfortunate this requires using a loader, tho... Would love to...

Reproductions here give me `ReferenceError: fakeAsync is not defined`, fwiw. A full standalone reproduction would allow me to verify if #13503 fixed the reported issue. You can also probably just...

@mhombach please give https://github.com/facebook/jest/releases/tag/v29.2.2 a try 🙂