[js] Update ts-jest 29.3.1 → 29.3.2 (patch) #735
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ ts-jest (29.3.1 → 29.3.2) · Repo · Changelog
Release Notes
29.3.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 37 commits:
chore(release): 29.3.2
fix: transpile `js` files from `node_modules` whenever Jest asks (#4791)
build(deps): Update dependency lint-staged to ^15.5.1
build: use faster mode to build/serve doc
build: fix npm audit issue for `website`
docs: add Hybrid Node module doc about `Node16/NodeNext`
test: add dynamic import code test for `transpile-module`
build(deps): Update dependency eslint-config-prettier to ^10.1.2
build(deps): Update dependency vite to ^6.2.6
build(deps): Update ESLint packages to ^8.29.1
build(deps): Update SonarSource/sonarqube-scan-action action to v5.1.0
docs: improve support ESM doc
fix: fix high severity issue for `website`
ci: don't run tests when there are only doc changes
refactor: remove unused codes in `json.ts`
test: use `ts` Jest config files for e2e tests
ci: configure Sonar code coverage
build(deps): Update dependency eslint to ^9.24.0
build(deps): Update dependency @eslint/js to ^9.24.0
build(deps): Update dependency type-fest to ^4.39.1
build(deps): Update dependency vite to ^6.2.5
build(deps): Update dependency eslint-plugin-prettier to ^5.2.6
build(deps): Update dependency @testing-library/react to ^16.3.0
build(deps): bump image-size from 1.1.1 to 1.2.1 in /website
docs: update README.md (#4772)
build(deps): Update dependency @types/react-dom to ^18.3.6
build(deps): Update dependency @eslint/compat to ^1.2.8
build(deps): Update dependency @types/node to v20.17.30
build(deps): Update dependency type-fest to ^4.39.0
build(deps): Update dependency @types/node to v20.17.29
docs: use code block title to display example file name
build(deps): Update dependency ts-jest to ^29.3.1
build(deps): Update ESLint packages to ^8.29.0
build(deps): Update dependency vite to ^6.2.4
build(deps): Update dependency esbuild to ~0.25.2
docs: improve `astTransformers` doc
docs: improve support ESM doc
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.