Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency ts-jest to v29 #41

Merged
merged 1 commit into from
Sep 18, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 18, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ts-jest (source) ^26.5.6 -> ^29.0.0 age adoption passing confidence

Release Notes

kulshekhar/ts-jest (ts-jest)

v29.1.1

Compare Source

Security Fixes
  • bump semver to 7.5.3

v29.1.0

Compare Source

Features

29.0.5 (2023-01-13)

Reverts

29.0.4 (2023-01-10)

Bug Fixes

29.0.3 (2022-09-28)

Bug Fixes
Features
  • add useESM option to pathsToModuleNameMapper options (#​3792) (eabe906)

29.0.2 (2022-09-23)

Bug Fixes

29.0.2 (2022-09-22)

Bug Fixes

29.0.1 (2022-09-13)

Bug Fixes
  • legacy: include existing globals config in cached config (#​3803) (e79be47)
Features
  • add typings for ts-jest options via transform config (#​3805) (664b0f2)

v29.0.5

Compare Source

Reverts

v29.0.4

Compare Source

Bug Fixes

v29.0.3

Compare Source

Bug Fixes
Features
  • add useESM option to pathsToModuleNameMapper options (#​3792) (eabe906)

v29.0.2

Compare Source

Bug Fixes

v29.0.1

Compare Source

Bug Fixes
  • legacy: include existing globals config in cached config (#​3803) (e79be47)
Features
  • add typings for ts-jest options via transform config (#​3805) (664b0f2)

v29.0.0

Compare Source

Features
DEPRECATIONS
  • Define ts-jest config under globals is now deprecated. Please define the config via transformer config instead.
BREAKING CHANGES
  • Only Node 14, 16 and 18 are supported
  • Jest 29 is required.

v28.0.8

Compare Source

Bug Fixes

v28.0.7

Compare Source

Bug Fixes

v28.0.6

Compare Source

Bug Fixes

v28.0.5

Compare Source

Bug Fixes

v28.0.4

Compare Source

Bug Fixes

v28.0.3

Compare Source

Bug Fixes

v28.0.2

Compare Source

Bug Fixes

v28.0.1

Compare Source

Bug Fixes

v28.0.0

Compare Source

Bug Fixes
  • legacy invoke Babel processAsync for babel-jest in ESM mode instead of process (#​3430) (0d7356c)
Features
BREAKING CHANGES
  • path-mapping AST transformer is no longer shipped in ts-jest v28. Please use an alternative one like https://github.com/LeDDGroup/typescript-transform-paths instead.
  • Any imports ts-jest/dist/compiler/ts-compiler should change to ts-jest/dist/legacy/compiler/ts-compiler
  • Any imports ts-jest/dist/compiler/ts-jest-compiler should change to ts-jest/dist/legacy/compiler/ts-jest-compiler
  • Any imports ts-jest/dist/config/config-set should change to ts-jest/dist/legacy/config/config-set
  • Minimum support TypeScript version is now 4.3 since Jest 28 requires it.
  • Jest 28 is required.
  • core: Any imports ts-jest/utils should be replaced with ts-jest.
  • core: Starting from Jest 27.4, mocked has been integrated into Jest repo.
  • core: Support for Node.js v10 has been removed as Jest drops support for it.

27.1.5 (2022-05-17)

Bug Fixes

27.1.4 (2022-03-24)

Bug Fixes

27.1.3 (2022-01-14)

Bug Fixes
  • compiler: update memory cache for compiler using received file content (#​3194) (e4d9541)

27.1.2 (2021-12-15)

Bug Fixes
  • stimulate esbuild type to avoid importing esbuild directly (#​3147) (9ace0a9)

27.1.1 (2021-12-07)

Bug Fixes

v27.1.5

Compare Source

Bug Fixes

v27.1.4

Compare Source

Bug Fixes

v27.1.3

Compare Source

Bug Fixes
  • compiler: update memory cache for compiler using received file content (#​3194) (e4d9541)

v27.1.2

Compare Source

Bug Fixes
  • stimulate esbuild type to avoid importing esbuild directly (#​3147) (9ace0a9)

v27.1.1

Compare Source

Bug Fixes

v27.1.0

Compare Source

Features
Code Refactoring

DEPRECATIONS

27.0.7 (2021-10-16)

Bug Fixes

27.0.6 (2021-10-14)

Bug Fixes

27.0.5 (2021-08-14)

Bug Fixes
Code Refactoring

27.0.4 (2021-07-21)

Bug Fixes
  • add @types/jest as optional peerDependencies to solve yarn 2 (#​2756) (5fbf43e)
  • add babel-jest as optional peerDependencies to solve yarn 2 (#​2751) (8bede2e)
  • config: include AST transformer's name and version into cache key (#​2755) (310fb9a), closes #​2753
Features

27.0.3 (2021-06-06)

Bug Fixes
Features

27.0.2 (2021-05-30)

Bug Fixes

27.0.1 (2021-05-26)

Bug Fixes

v27.0.7

Compare Source

Bug Fixes

v27.0.6

Compare Source

Bug Fixes

v27.0.5

Compare Source

Bug Fixes
Code Refactoring

v27.0.4

Compare Source

Bug Fixes
  • add @types/jest as optional peerDependencies to solve yarn 2 (#​2756) (5fbf43e)
  • add babel-jest as optional peerDependencies to solve yarn 2 (#​2751) (8bede2e)
  • config: include AST transformer's name and version into cache key (#​2755) (310fb9a), closes #​2753
Features

v27.0.3

Compare Source

Bug Fixes
Features

v27.0.2

Compare Source

Bug Fixes

v27.0.1

Compare Source

Bug Fixes

v27.0.0

Compare Source

Bug Fixes
Features
Performance Improvements
  • reuse jest file system cache for isolatedModules: false (#​2189) (68f446b)
Code Refactoring

BREAKING CHANGES

import type { TsCompilerInstance } from 'ts-jest/dist/types'

export function factory(compilerInstance: TsCompilerInstance) {
   //...
}
  • One is currently using pathRegex should use exclude with glob patterns.
  • If one currently relies on type check for js files, please set checkJs: true in your tsconfig.
  • Now both isolatedModules: true and isolatedModule: false codes are in one single class TsCompiler which is an instance created in TsJestCompiler based on config option compiler with value typescript or ttypescript.
  • config: packageJson config option is not used in internal ts-jest so this option is now removed.
  • config: One is defining ast transformers in jest.config.js/package.json should change to
// jest.config.js
module.exports = {
   //...
   globals: {
      'ts-jest': {
         astTransformers: {
           before: ['your_before_transformer_path'],
           after: ['your_after_transformer_path'],
           afterDeclarations: ['your_afterDeclarations_transformer_path'],
         }
      }
   }
}

or

// package.json
{
  "jest": {
     "globals": {
        "ts-jest": {
           "astTransformers": {
              "before": ["your_before_transformer_path"],
              "after": ["your_after_transformer_path"],
              "afterDeclarations": ["your_afterDeclarations_transformer_path"]
           }
        }
     }
  }
}
  • One currently refers type in jest.config.js
/** @​typedef {import('ts-jest')} */
module.exports = {
  //...
}

should change to

/** @​typedef {import('ts-jest/dist/types')} */
module.exports = {
  //...
}
  • Remove possibilities to import mocked, createJestPreset, pathsToModuleNameMapper from package entry. One should change to
import { mocked, createJestPreset, pathsToModuleNameMapper } from 'ts-jest/utils'
  • config: One currently uses tsConfig should change to tsconfig in your jest.config.js or package.json.

26.5.6 (2021-05-05)

Code Refactoring
  • refactor(config): show warning message for sourceMap: false (#​2557) (cf60990).

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot enabled auto-merge (rebase) September 18, 2023 06:26
@renovate
Copy link
Contributor Author

renovate bot commented Sep 18, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @edx/[email protected]
npm ERR! Found: @edx/[email protected]
npm ERR! node_modules/@edx/frontend-build
npm ERR!   dev @edx/frontend-build@"12.9.0-alpha.6" from the root project
npm ERR!   peer @edx/frontend-build@">= 8.1.0 || ^12.9.0-alpha.1" from @edx/[email protected]
npm ERR!   node_modules/@edx/frontend-platform
npm ERR!     @edx/frontend-platform@"5.3.2" from the root project
npm ERR!     peer @edx/frontend-platform@"^4.0.0 || ^5.0.0" from @edx/[email protected]
npm ERR!     node_modules/@edx/frontend-component-footer
npm ERR!       @edx/frontend-component-footer@"12.2.1" from the root project
npm ERR!     1 more (@edx/frontend-component-header)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @edx/frontend-build@">=8.1.0" from @edx/[email protected]
npm ERR! node_modules/@edx/react-unit-test-utils
npm ERR!   @edx/react-unit-test-utils@"1.7.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @edx/[email protected]
npm ERR! node_modules/@edx/frontend-build
npm ERR!   peer @edx/frontend-build@">=8.1.0" from @edx/[email protected]
npm ERR!   node_modules/@edx/react-unit-test-utils
npm ERR!     @edx/react-unit-test-utils@"1.7.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/f8cfb6/4cc7b4/cache/others/npm/_logs/2023-09-18T13_21_11_830Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/f8cfb6/4cc7b4/cache/others/npm/_logs/2023-09-18T13_21_11_830Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-jest-monorepo branch from 0292343 to 471c1e7 Compare September 18, 2023 09:28
@renovate renovate bot force-pushed the renovate/major-jest-monorepo branch from 471c1e7 to b3a44e2 Compare September 18, 2023 13:21
@renovate renovate bot merged commit 57a5036 into master Sep 18, 2023
@renovate renovate bot deleted the renovate/major-jest-monorepo branch September 18, 2023 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants