You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The motivation for this is not so much any particular problem with jest as the desire to move from targeting CommonJS modules (CJS) to EcmaScript modules (ESM) in our build system:
CJS modules interoperate poorly with ESM packages from NPM, of which there are a growing number. This has caused us to use older versions of various packages instead of the latest.
Faster native-speed tooling for building TypeScript tends to have poor or non-existent support for CJS. Targeting CJS therefore locks us into using slower build tools.
vitest has a very similar API and DX to jest, but has much better support for ESM. It uses faster native-speed tooling-esbuild at the moment-though the gains appear to be uneven. So I wouldn't necessarily consider this to be a net performance win.
(See also the official guide)
The motivation for this is not so much any particular problem with
jest
as the desire to move from targeting CommonJS modules (CJS) to EcmaScript modules (ESM) in our build system:vitest
has a very similar API and DX tojest
, but has much better support for ESM. It uses faster native-speed tooling-esbuild at the moment-though the gains appear to be uneven. So I wouldn't necessarily consider this to be a net performance win.Progress
The text was updated successfully, but these errors were encountered: