Skip to content

Bump jest and @types/jest - #5

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/multi-cbfe5253e3
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/multi-cbfe5253e3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 29, 2026

Copy link
Copy Markdown

Bumps jest and @types/jest. These dependencies needed to be updated together.
Updates jest from 29.7.0 to 30.4.2

Release notes

Sourced from jest's releases.

v30.4.2

Fixes

  • [jest-runtime] Fix named imports from CJS modules whose module.exports is a function with own-property exports (#16150)

Full Changelog: jestjs/jest@v30.4.1...v30.4.2

v30.4.1

Features

  • [jest-config, jest-core, jest-runner, jest-schemas, jest-types] Allow custom runner configuration options via tuple format ['runner-path', {options}] (#16141)

Fixes

  • [jest-runtime] Align CJS-from-ESM default export with Node: module.exports is always the ESM default, __esModule unwrapping is no longer applied (#16143)

Full Changelog: jestjs/jest@v30.4.0...v30.4.1

v30.4.0

Big release! 😀

Main feature is a rewrite of our custom runtime in preparation for stabilisation of native support of ESM. As part of that work require(esm) module is now supported on Node 24.9+ (still requires --experimental-vm-modules like before).

In addition we now support fake timers for the recently released Temporal API in Node v26.

React 19 is also supported properly in pretty-format, meaning snapshots of React components now work like they should.

Due to all the changes, there might be regressions that snuck in. Please report them!

Full list of changes below

Features

  • [babel-jest] Support collecting coverage from .mts, .cts (and other) files (#15994)
  • [jest-circus, jest-cli, jest-config, jest-core, jest-jasmine2, jest-types] Add --collect-tests flag to discover and list tests without executing them (#16006)
  • [jest-config, jest-runner, jest-worker] Add workerGracefulExitTimeout config option to control how long workers are given to exit before being force-killed (#15984)
  • [jest-config] Add support for jest.config.mts as a valid configuration file (#16005)
  • [jest-config, jest-core, jest-reporters, jest-runner] verbose and silent can now be set per-project; the project-level value overrides the global value for that project's tests (#16133)
  • [@jest/fake-timers] Accept Temporal.Duration in jest.advanceTimersByTime() and jest.advanceTimersByTimeAsync() (#16128)
  • [@jest/fake-timers] Accept Temporal.Instant and Temporal.ZonedDateTime in jest.setSystemTime() and useFakeTimers({now}) (#16128)
  • [@jest/fake-timers] Support faking Temporal.Now.* (#16131)
  • [jest-mock] Add clearMocksOnScope(scope) on ModuleMocker for clearing every mock function exposed on a scope object (#16088)
  • [jest-resolve] Add canResolveSync() on Resolver so callers can detect when a user-configured resolver only exports an async hook (#16064)
  • [jest-runtime] Use synchronous evaluate() for ES modules without top-level await on Node versions that support it (v24.9+), and prefer the synchronous transform path when a sync transformer is configured (#16062)
  • [jest-runtime] Support require() of ES modules on Node v24.9+ (#16074)
  • [jest-runtime] Validate TC39 import attributes (with { type: 'json' }) on ESM imports (#16127)
  • [@jest/transform] Add canTransformSync(filename) on ScriptTransformer so callers can pick the sync vs async transform path (#16062)
  • [jest-util] Add isError helper (#16076)

... (truncated)

Changelog

Sourced from jest's changelog.

30.4.2

Fixes

  • [jest-runtime] Fix named imports from CJS modules whose module.exports is a function with own-property exports (#16150)

30.4.1

Features

  • [jest-config, jest-core, jest-runner, jest-schemas, jest-types] Allow custom runner configuration options via tuple format ['runner-path', {options}] (#16141)

Fixes

  • [jest-runtime] Align CJS-from-ESM default export with Node: module.exports is always the ESM default, __esModule unwrapping is no longer applied (#16143)

30.4.0

Features

  • [babel-jest] Support collecting coverage from .mts, .cts (and other) files (#15994)
  • [jest-circus, jest-cli, jest-config, jest-core, jest-jasmine2, jest-types] Add --collect-tests flag to discover and list tests without executing them (#16006)
  • [jest-config, jest-runner, jest-worker] Add workerGracefulExitTimeout config option to control how long workers are given to exit before being force-killed (#15984)
  • [jest-config] Add support for jest.config.mts as a valid configuration file (#16005)
  • [jest-config, jest-core, jest-reporters, jest-runner] verbose and silent can now be set per-project; the project-level value overrides the global value for that project's tests (#16133)
  • [@jest/fake-timers] Accept Temporal.Duration in jest.advanceTimersByTime() and jest.advanceTimersByTimeAsync() (#16128)
  • [@jest/fake-timers] Accept Temporal.Instant and Temporal.ZonedDateTime in jest.setSystemTime() and useFakeTimers({now}) (#16128)
  • [@jest/fake-timers] Support faking Temporal.Now.* (#16131)
  • [jest-mock] Add clearMocksOnScope(scope) on ModuleMocker for clearing every mock function exposed on a scope object (#16088)
  • [jest-resolve] Add canResolveSync() on Resolver so callers can detect when a user-configured resolver only exports an async hook (#16064)
  • [jest-runtime] Use synchronous evaluate() for ES modules without top-level await on Node versions that support it (v24.9+), and prefer the synchronous transform path when a sync transformer is configured (#16062)
  • [jest-runtime] Support require() of ES modules on Node v24.9+ (#16074)
  • [jest-runtime] Validate TC39 import attributes (with { type: 'json' }) on ESM imports (#16127)
  • [@jest/transform] Add canTransformSync(filename) on ScriptTransformer so callers can pick the sync vs async transform path (#16062)
  • [jest-util] Add isError helper (#16076)
  • [pretty-format] Support React 19 (#16123)

Fixes

  • [expect-utils] Fix toStrictEqual failing on structuredClone results due to cross-realm constructor mismatch (#15959)
  • [@jest/expect-utils] Prevent toMatchObject/subset matching from throwing when encountering exotic iterables (#15952)
  • [fake-timers] Convert Date to milliseconds before passing to @sinonjs/fake-timers (#16029)
  • [jest] Export GlobalConfig and ProjectConfig TypeScript types (#16132)
  • [jest-circus] Prevent crash when asyncError is undefined for non-Error throws (#16003)
  • [jest-circus, jest-jasmine2] Include Error.cause in JSON failureMessages output (#15967)
  • [jest-config] Fix preset path resolution on Windows when the preset uses subpath exports (#15961)
  • [jest-config] Allow collectCoverage and coverageProvider in project config without a validation warning (#16132)
  • [jest-config] Project config validator now emits "is not supported in an individual project configuration" instead of "probably a typing mistake" for known global-only options (#16132)
  • [jest-environment-node] Fix --localstorage-file warning on Node 25+ (#16086)
  • [jest-reporters] Apply global coverage threshold to unmatched pattern files in addition to glob/path thresholds (#16137)

... (truncated)

Commits

Updates @types/jest from 29.5.14 to 30.0.0

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [jest](https://github.com/jestjs/jest/tree/HEAD/packages/jest) and [@types/jest](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/jest). These dependencies needed to be updated together.

Updates `jest` from 29.7.0 to 30.4.2
- [Release notes](https://github.com/jestjs/jest/releases)
- [Changelog](https://github.com/jestjs/jest/blob/main/CHANGELOG.md)
- [Commits](https://github.com/jestjs/jest/commits/v30.4.2/packages/jest)

Updates `@types/jest` from 29.5.14 to 30.0.0
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/jest)

---
updated-dependencies:
- dependency-name: jest
  dependency-version: 30.4.2
  dependency-type: direct:development
  update-type: version-update:semver-major
- dependency-name: "@types/jest"
  dependency-version: 30.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 29, 2026
walhalabi-code added a commit that referenced this pull request Aug 30, 2026
The suite fails on a fresh clone on Windows, and has since the repository was
created. Git's core.autocrlf is on by default there, so checkout rewrites text
files to CRLF; test/ai.test.ts asserts body.startsWith('---\n') on a generated
skill file, which is false once the bytes on disk are ---\r\n.

CI never saw it because Linux runners check out LF, and the maintainer's working
copy predates any checkout so it still holds the original LF. Only someone
cloning fresh on Windows hits it, which is to say a new contributor on their
first npm test.

The stored blobs are already LF, so this changes checkout behaviour only and no
file content moves.

Found while investigating why Dependabot PR #5 failed. That turned out to be
unrelated: its lockfile is out of sync with its package.json, so every job dies
at npm ci before a test runs. jest 30 itself is fine - 332 of 334 pass on it,
and the single failure is this line-ending bug, which reproduces identically on
jest 29.

Co-authored-by: Waseem Alhalabi <217769131+walhalabi-code@users.noreply.github.com>
@dependabot @github

dependabot Bot commented on behalf of github Aug 30, 2026

Copy link
Copy Markdown
Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/multi-cbfe5253e3 branch August 30, 2026 11:51
walhalabi-code added a commit that referenced this pull request Aug 31, 2026
All five checks failed in under 40 seconds, which is the npm ci signature: it
refuses a package.json and package-lock.json that disagree, and every job runs
it before anything else.

Making @types/parse a required peer rather than an optional one changed the
dependency tree, and the lock was not regenerated to match:

  npm error Missing: @types/parse@3.0.9 from lock file

This is the same failure diagnosed in Dependabot PR #5 earlier today - a
lockfile out of step with its package.json, killing every job before a single
test runs. Worth noting that the lesson did not transfer on the first try.

Also picks up the 3.0.0 -> 3.0.1 version bump in the lock's root entry.

Checked while regenerating: installing @types/parse alongside the library's own
src/global.d.ts does not collide. That file is not shipped - dist carries no
global.d.ts - so a consumer only ever sees @types/parse.
walhalabi-code added a commit that referenced this pull request Aug 31, 2026
* Act on the first round of hands-on testing

Seven findings from using the published package the way a stranger would.

@types/parse was declared an optional peer, but the shipped declarations
require it: BaseModel is typed as extending Parse.Object. Without it,
TypeScript reports "Cannot find namespace 'Parse'" and then "Property 'save'
does not exist on type 'Note'" - errors that point at the user's own model
rather than the missing package. It is now a required peer.

psk new installs the generated project's dependencies. Scaffolding something
that cannot run until you read the next line of output was a needless step.
--no-install opts out; a failed install warns and puts the step back in the
next-steps list rather than leaving a project that looks finished.

The generated project can be tested. It had no runner, no example and no test
script, which sat badly against a library that argues for verification. It now
uses Node's own runner - nothing to install, no config - and ships five tests
covering the failures that raise no error: that a field written on a model
actually reaches Parse, that save() would send it, and that the schema rules
are enforced.

npm audit is clean in a new project. The 14 advisories all came from
transitive pins in parse-server's tree, none of them fixable by bumping a peer
because parse 8.6.0 is the latest and pins ws exactly. Overrides to the
patched versions of ws, follow-redirects, ip-address and uuid take it to zero.
Verified that parse-server still loads and the project still builds under
them.

listNotes demonstrates real pagination. It returned results.length as the
count - the size of the page you already have, which tells a client nothing.
It now uses withCount() for the true total in one round trip, and returns
limit, skip and hasMore.

The CLI no longer describes itself as broken. "The mistakes this library fails
silently on" was meant as "mistakes that produce no error", but it parses as
"this library fails silently" - printed after every psk new. The mistake is
now the subject, not the library.

psk new says something when it lands inside another npm project, and seed.ts
is 254 lines rather than 325, with the same behaviour and half the commentary.

Docs, website and the generated README follow the CLI: six quickstart blocks,
the --no-install flag, a Tests section, corrected file counts, and the search
index, which duplicates page text and had gone stale again.

334 library tests pass. A generated project compiles, passes its own five
tests, and audits clean.

* Regenerate the lockfile for the required @types/parse peer

All five checks failed in under 40 seconds, which is the npm ci signature: it
refuses a package.json and package-lock.json that disagree, and every job runs
it before anything else.

Making @types/parse a required peer rather than an optional one changed the
dependency tree, and the lock was not regenerated to match:

  npm error Missing: @types/parse@3.0.9 from lock file

This is the same failure diagnosed in Dependabot PR #5 earlier today - a
lockfile out of step with its package.json, killing every job before a single
test runs. Worth noting that the lesson did not transfer on the first try.

Also picks up the 3.0.0 -> 3.0.1 version bump in the lock's root entry.

Checked while regenerating: installing @types/parse alongside the library's own
src/global.d.ts does not collide. That file is not shipped - dist carries no
global.d.ts - so a consumer only ever sees @types/parse.

---------

Co-authored-by: Waseem Alhalabi <217769131+walhalabi-code@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant