chore: use @swc/jest vs ts-jest #1457
Conversation
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 075053d:
|
|
Cool, so migrating to |
kettanaito
force-pushed
the
chore/use-swc
branch
from
814778d to
fa198d3
Compare
| @@ -3,6 +3,8 @@ import * as path from 'path' | |||
| import chalk from 'chalk' | |||
| import { until } from '@open-draft/until' | |||
|
|
|||
| const { cyan } = chalk | |||
There was a problem hiding this comment.
Missed this chalk import usage in #1399.
| /** | ||
| * @jest-environment node | ||
| */ | ||
| import https from 'https' |
There was a problem hiding this comment.
Note
Do not use wild import. Do use allowSyntheticDefaultImport in TypeScript. This makes @swc/jest happy. Otherwise, module patching from the interceptors applies patches to a different export methods than the test gets.
Released: v0.48.3 🎉This has been released in v0.48.3! Make sure to always update to the latest version ( Predictable release automation by @ossjs/release. |
Adopts
@swc/jestas a replacement forts-jest.@swc/jestis more performant and doesn't have memory issues thatts-jesthas.