Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@storybook/jest

Package Overview
Dependencies
Maintainers
31
Versions
80
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@storybook/jest

Instrumented version of Jest for Storybook Interactions

  • 0.1.1-next.1
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
371K
decreased by-23.24%
Maintainers
31
Weekly downloads
 
Created
Source

Storybook Jest

Storybook integration for Jest, instrumented for use with the Interactions addon.

FAQ

Typescript does not recognize expect().toBeInTheDocument()

This is likely an issue with newer package managers.

The @storybook/jest package provides some type augmentations so that expect has extended matchers coming from Testing Library. The way it works, is that @storybook/jest depends on @testing-library/jest-dom, a package that depends on @types/testing-library__jest-dom. That @types package should be hoisted in your project in order for your types to fully work. As a result, you should have a node_modules/@types/testing-library__jest-dom directory. If you don't, then the types won't exist and that's why you're having issues.

For instance, if you have a yarn project, hoisting happens automatically. However if you're using pnpm, @types are not hoisted automatically, you will have to add a .npmrc file with the following setting:

// .npmrc
public-hoist-pattern[]=@types*

Otherwise, installing @types/testing-library__jest-dom as a direct dependency should have the same effect and fix your issue.

If you are still experiencing issues after making these changes, it's very likely that your tsconfig.json file contains specific type overrides, which means that it will ignore automatic types, for instance:

{
  "compilerOptions": {
    "types": [
      "node",
      "mocha",
    ]
  }
}

In that case, make sure to add testing-library__jest-dom to the types array:

{
  "compilerOptions": {
    "types": [
      "node",
      "mocha",
      "testing-library__jest-dom"
    ]
  }
}

FAQs

Package last updated on 19 Jun 2023

Did you know?

Socket

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.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc