jest-matcher-specific-error
Advanced tools
Make sure your function really throws what you expect
Make sure your function really throws what you expect
Workaround for https://github.com/facebook/jest/issues/8140
With npm:
npm install --save-dev jest-matcher-specific-error
With yarn:
yarn add -D jest-matcher-specific-error
Same as Other jest matchers
await expect(yourPromise).rejects.toMatchError(expectedError);
await expect(yourFunction).rejects.toMatchError(expectedError);
expect(yourError).toMatchError(expectedError);
Errors threated as equal if ALL conditions satisfied:
=== comparison by reference)jest helper comparison)Error stack traces are ignored.
FAQs
Make sure your function really throws what you expect
We found that jest-matcher-specific-error demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.