ts-jest 29.4.7 → 29.4.8

package/.opencode/plans/pr6.md

@@ -1,178 +0,0 @@
-# PR 6 — Promote + Cleanup
-
-## Overview
-
-Promotes the new transformer as the default. Swaps `src/index.ts` so `createTransformer` uses
-the new transformer by default. Adds a deprecation path for `future.v30_newTransformer: false`.
-Also fixes the ESM interop false-positive warning in the legacy config and removes long-deprecated
-type aliases.
-
-**User-visible change**: YES — default behavior changes
-**Depends on**: PR 5
-**Files modified**: `src/index.ts`, `src/legacy/config/config-set.ts`, `src/types.ts`
-
----
-
-## Files to Modify
-
-```
-src/index.ts                          — swap default; add legacy deprecation warning
-src/legacy/config/config-set.ts       — fix ESM interop false-positive
-src/types.ts                          — remove deprecated type aliases
-```
-
----
-
-## Requirements
-
-### `src/index.ts` — Default swap
-
-```ts
-export const createTransformer = (tsJestConfig?: TsJestTransformerOptions) => {
-  if (tsJestConfig?.future?.v30_newTransformer === false) {
-    // Explicit opt-out — use legacy with deprecation warning
-    logger.warn(
-      'future.v30_newTransformer: false is deprecated. ' +
-        'The v30 transformer is now the default. ' +
-        'Use ts-jest/legacy if you need the legacy transformer.',
-    )
-    return new TsJestTransformer(tsJestConfig)
-  }
-  // Default: new transformer
-  const { NewTsJestTransformer } = require('./experimental/transformer/transformer')
-  return new NewTsJestTransformer(tsJestConfig)
-}
-```
-
-`ts-jest/legacy` entry point stays unchanged as a permanent escape hatch.
-`future.v30_newTransformer: true` still works silently (no warning, same as default now).
-
----
-
-### `src/legacy/config/config-set.ts` — ESM interop false-positive fix
-
-**Location**: lines 487–500 (ESM interop warning block)
-
-**Current condition** (warns for these module kinds):
-
-```
-NOT in [CommonJS, Node16, NodeNext]
-```
-
-**Fixed condition** (also exclude modern ESM kinds that don't need the warning):
-
-```
-NOT in [CommonJS, Node16, NodeNext, ESNext, ES2015, ES2016, ES2017, ES2018, ES2019, ES2020, ES2021, ES2022]
-```
-
-This is the only change to `config-set.ts`. The fix applies to the **legacy** transformer as well
-(not just the new one) since it's a genuine false positive.
-
-**Rationale**: Projects using `module: ESNext` in modern setups with `"type": "module"` in
-package.json get a spurious warning even though ESM interop is not needed. ESNext/ES2015–ES2022
-modules handle default imports correctly.
-
----
-
-### `src/types.ts` — Remove deprecated type aliases
-
-Remove the following aliases that have been deprecated since v28:
-
-```ts
-// REMOVE these deprecated aliases:
-/** @deprecated use TsJestTransformerOptions */
-export type TsJestGlobalOptions = TsJestTransformerOptions
-
-/** @deprecated use Config.ProjectConfig */
-export type ProjectConfigTsJest = Config.ProjectConfig
-
-/** @deprecated use Config.InitialOptions */
-export type InitialOptionsTsJest = Config.InitialOptions
-```
-
-**Note**: `TsJestTransformerOptions` itself (the non-alias) is kept unchanged.
-Do not remove `TsJestCompileOptions`, `CompiledOutput`, `AstTransformerDesc`, `CompilerInstance`,
-or `TsCompilerInstance`.
-
----
-
-## Migration Guide (to include in PR description)
-
-### Users of `ts-jest` (no config change needed)
-
-The new transformer is now the default. If you encounter issues:
-
-```js
-// Temporary escape hatch
-transform: { '^.+\\.tsx?$': 'ts-jest/legacy' }
-```
-
-### Users of `future.v30_newTransformer: true`
-
-Remove the flag — it's now the default and will be cleaned up in v31.
-
-### Users of `future.v30_newTransformer: false`
-
-Switch to `ts-jest/legacy` explicitly. The `false` value emits a deprecation warning.
-
-### Users of `diagnostics: false`
-
-Replace with `noCheck: true` in your tsconfig:
-
-```json
-{ "compilerOptions": { "noCheck": true } }
-```
-
-### Users of `isolatedModules: true` (ts-jest option)
-
-Move it to tsconfig:
-
-```json
-{ "compilerOptions": { "isolatedModules": true } }
-```
-
-Type checking now works correctly with `isolatedModules: true` (this was a bug in the old transformer).
-
-### Users of deprecated type aliases
-
-| Old                    | New                        |
-| ---------------------- | -------------------------- |
-| `TsJestGlobalOptions`  | `TsJestTransformerOptions` |
-| `ProjectConfigTsJest`  | `Config.ProjectConfig`     |
-| `InitialOptionsTsJest` | `Config.InitialOptions`    |
-
----
-
-## Test Requirements
-
-- Update `src/index.spec.ts` to verify:
-
-  - No `future` flag → new transformer instantiated
-  - `future.v30_newTransformer: true` → new transformer (no warning)
-  - `future.v30_newTransformer: false` → legacy transformer + deprecation warning
-
-- Update `src/legacy/config/config-set.spec.ts` for ESM interop warning fix:
-
-  - `module: ESNext` → no warning emitted
-  - `module: ES2020` → no warning emitted
-  - `module: AMD` → warning still emitted (not in exclusion list)
-
-- All existing e2e tests must remain green (legacy behavior unchanged for `ts-jest/legacy` users)
-
-- Add e2e scenario: `e2e/v30-default/` — verifies that bare `ts-jest` (no future flag) uses new
-  transformer and produces correct output
-
----
-
-## Acceptance Criteria
-
-- [ ] `createTransformer()` with no options → new transformer
-- [ ] `future.v30_newTransformer: false` → legacy transformer + deprecation warning in stderr
-- [ ] `ts-jest/legacy` → legacy transformer, no warning
-- [ ] `module: ESNext` in tsconfig → no ESM interop warning (legacy fix)
-- [ ] `module: ES2020` in tsconfig → no ESM interop warning (legacy fix)
-- [ ] `module: AMD` in tsconfig → ESM interop warning still fires
-- [ ] Deprecated type aliases `TsJestGlobalOptions`, `ProjectConfigTsJest`, `InitialOptionsTsJest` removed
-- [ ] All e2e tests pass
-- [ ] `tsc --noEmit` passes
-- [ ] `CHANGELOG` updated with migration notes