4 ms·
Looks to me it will be dead soon if they don't figure out how to handle ESM imports. More and more libraries stop packaging commonjs for their new versions. I'v
by azangru 1y ago
Looks to me it will be dead soon if they don't figure out how to handle ESM imports. More and more libraries stop packaging commonjs for their new versions. I've been bitten first by d3, then by graphql-request (now graffle), then by msw, then by faker-js. Faker-js, for god's sake! They write in their docs that since version 10, they are incompatible with Jest [0]. Jest seems to be going the way of Enzyme and dodo.
The maintainer of MSW has been screaming for years for people to drop jest [1]
[0] - https://github.com/faker-js/faker/blob/428ff3328b4c4b13ec29d646eea7c4ea98522323/docs/guide/upgrading.md?plain=1#L50 https://github.com/faker-js/faker/blob/428ff3328b4c4b13ec29d...
[1] - https://x.com/kettanaito/status/1746165619731382351#m https://x.com/kettanaito/status/1746165619731382351#m
- sunaookami 1y agoMan we have started with Jest tests for our React Native App half a year ago and now we should already drop it? What should we use instead?? Vitest? How's the compatibility? I'm so exhausted man, glad I'm qutting JS dev soon hopefully.
- azangru 1y agoVitest, yes. Compatibility with jest is great. The ultimate win, of course, would be to use the native Node test runner. See the sourse of the Node.js website - I think they have pulled it off despite running a Node.js app.
- isaachinman 1y agoProblem with vitest is that there's no first class caching if I recall correctly