Skip to content

Releases: storybookjs/addon-coverage

v3.0.0

10 Nov 13:33

Choose a tag to compare

πŸ’₯ Breaking Change

Warning

If you're using Storybook in a Vite-based project, you might want to use Storybook's Vitest integration instead. It's faster, provides code coverage out of the box (so you don't need this addon anymore), and integrates well with all Storybook's latest features.

Authors: 2

v2.0.0

12 Jun 07:22

Choose a tag to compare

πŸ’₯ Breaking Change

  • Update dependencies and package structure to support ESM #51 (@yannbf)

πŸ› Bug Fix

Authors: 1

v1.0.5

24 Dec 10:40

Choose a tag to compare

πŸ› Bug Fix

  • fix: Handling of rawSourceMap string type in webpack5-istanbul-loader #44 (@mschimk1)

Authors: 1

v1.0.4

24 May 12:54

Choose a tag to compare

πŸ› Bug Fix

Authors: 1

v1.0.3

07 May 07:17

Choose a tag to compare

πŸ› Bug Fix

  • Fix: Handle scenario where rawSourceMap is a string #33 (@hkaikai)

Authors: 1

v1.0.2

07 May 07:14

Choose a tag to compare

πŸ› Bug Fix

Authors: 1

v1.0.1

28 Feb 08:23

Choose a tag to compare

πŸ› Bug Fix

πŸ“ Documentation

Authors: 2

v1.0.0

14 Nov 11:38

Choose a tag to compare

Release Notes

[Breaking Change]: Replace babel-istanbul-plugin and replace it by a webpack loader (#27)

  • [BREAKING CHANGE]: Dropping Storybook < 7 support
  • Replaced babel-istanbul-plugin with a custom Webpack loader to support coverage independently of the compiler used for Webpack5 projects. Before, the coverage addon only worked if Babel was used with Webpack5. Now, users might use other compilers like, for example, SWC.

πŸ’₯ Breaking Change

πŸ› Bug Fix

Authors: 2

v0.0.9

20 Jul 08:50

Choose a tag to compare

⚠️ Pushed to main

Authors: 1

v0.0.8

06 Feb 19:11

Choose a tag to compare

πŸ› Bug Fix

  • Set forceBuildInstrument only in production builds #16 (@yannbf)

Authors: 1