Jacob Klapwijk

@kettanaito > Despite the parallelization in Jest, it still only spawns 1 process. The parallelization may happen via threads/child processes to achieve the execution of multiple test suites simultaneously. The...

I'm guessing that [this issue](https://github.com/ably/ably-js/issues/983) (and [this fix](https://github.com/ably/ably-js/pull/984)) also would've been caught by these.

Would it be possible to even skip the commit message editor? The subsequent step is anyway `git reset --hard HEAD~1`, I'm guessing that the merge only happens to verify that...

Assuming that you don't actually need to test the internals of Spin.js, you can mock it: in your Jest config: ```js moduleNameMapper": { "spin.js": "/test/__mocks__/spinMock.js", }, ``` in spinMock.js: ```js...

- Bisecting indicates that this commit: 647c93e4d036a9f506cad329e687780be09cafa9 causes the bug. - I've added a regression test in this commit https://github.com/JCB-K/next.js/commit/5478ce1e59d20d1f80f8b89187ff55cfd3daa446 - Some further debugging indicates that [this code](https://github.com/vercel/next.js/blob/canary/packages/next/client/link.tsx#L286-L292) causes the...

Sure thing, but I first want to do a refactoring. The code is pretty crude right now but then again, I wrote it 2 years ago. I don't use it...

Here is a repro case, using Next.js and Joy: https://codesandbox.io/p/devbox/tender-albattani-7pdqjs It's important to use Next.js in order to repro this issue, it uses React's canary release internally, which is on...