- From version 3.4.x to 4.0.x
- From version 3.3.x to 3.4.x
- From version 3.2.x to 3.3.x
- From version 3.1.x to 3.2.x
- From version 3.0.x to 3.1.x
- From version 2.x.x to 3.x.x
With 4.0 as our first major release in over a year, we've collected a lot of cleanup tasks. All deprecations have been marked for months, so we hope that there will be no significant impact on your project.
- Addon Panel to
Z - Stories Panel to
X - Show Search to
O - Addon Panel right side to
G
Addon-info's addWithInfo has been marked deprecated since 3.2. In 4.0 we've removed it completely. See the package README for the proper usage.
The @storybook/react-native had built-in addons (addon-actions and addon-links) that have been marked as deprecated since 3.x. They have been fully removed in 4.x. If your project still uses the built-ins, you'll need to add explicit dependencies on @storybook/addon-actions and/or @storybook/addon-links and import directly from those packages.
imageSnapshottest function was extracted fromaddon-storyshotsand moved to a new package -addon-storyshots-puppeteerthat now will be dependant on puppeteergetSnapshotFileNameexport was replaced with theStories2SnapsConverterclass that now can be overridden for a custom implementation of the snapshot-name generation
There are no expected breaking changes in the 3.4.x release, but 3.4 contains a major refactor to make it easier to support new frameworks, and we will document any breaking changes here if they arise.
There wasn't expected be any breaking changes in this release, but unfortunately it turned out that there are some. We're revisiting our release strategy to follow semver more strictly.
Also read on if you're using addon-knobs: we advise an update to your code for efficiency's sake.
babel-core is now a peer dependency (#2494)
This affects you if you don't use babel in your project. You may need to add babel-core as dev dependency:
npm install --save-dev babel-core
This was done to support different major versions of babel.
Base webpack config now contains vital plugins (#1775)
This affects you if you use custom webpack config in Full Control Mode while not preserving the plugins from storybookBaseConfig. Before 3.3, preserving them was just a reccomendation, but now it became a requirement.
Knobs users: there was a bug in 3.2.x where using the knobs addon imported all framework runtimes (e.g. React and Vue). To fix the problem, we refactored knobs. Switching to the new style is easy:
In the case of React or React-Native, import knobs like this:
import { withKnobs, text, boolean, number } from '@storybook/addon-knobs/react';In the case of Vue: import { ... } from '@storybook/addon-knobs/vue';
In the case of Angular: import { ... } from '@storybook/addon-knobs/angular';
NOTE: technically this is a breaking change, but only if you use TypeScript. Sorry people!
TypeScript users: we've moved the rest of our addons type definitions into DefinitelyTyped. Starting in 3.2.0 make sure to use the right addons types:
npm install @types/storybook__addon-notes @types/storybook__addon-options @types/storybook__addon-knobs @types/storybook__addon-links --save-devSee also TypeScript definitions in 3.1.x.
We're in the process of upgrading our addons APIs. As a first step, we've upgraded the Info and Notes addons. The old API will still work with your existing projects, but will be deprecated soon and removed in Storybook 4.0.
Here's an example of using Notes and Info in 3.2 with the new API.
storiesOf('composition', module)
.add('new addons api',
withInfo('see Notes panel for composition info')(
withNotes({ text: 'Composition: Info(Notes())' })(context =>
<MyComponent name={context.story} />
)
)
);It's not beautiful, but we'll be adding a more convenient/idiomatic way of using these withX primitives in Storybook 3.3.
NOTE: technically this is a breaking change and should be a 4.0.0 release according to semver. However, we're still figuring things out, and didn't think this change necessitated a major release. Please bear with us!
TypeScript users: we are in the process of moving our typescript definitions into DefinitelyTyped. If you're using TypeScript, starting in 3.1.0 you need to make sure your type definitions are installed:
npm install @types/node @types/react @types/storybook__react --save-devWe have deprecated the use of head.html for including scripts/styles/etc. into stories, though it will still work with a warning.
Now we use:
preview-head.htmlfor including extra content into the preview pane.manager-head.htmlfor including extra content into the manager window.
Read our docs for more details.
This major release is mainly an internal restructuring. Upgrading requires work on behalf of users, this was unavoidable. We're sorry if this inconveniences you, we have tried via this document and provided tools to make the process as easy as possible.
Storybook will now use webpack 2 (and only webpack 2).
If you are using a custom webpack.config.js you need to change this to be compatible.
You can find the guide to upgrading your webpack config on webpack.js.org.
All our packages have been renamed and published to npm as version 3.0.0 under the @storybook namespace.
To update your app to use the new package names, you can use the cli:
npm install --global @storybook/cli
# if you run this inside a v2 app, it should perform the necessary codemods.
getstorybookIf the above doesn't work, or you want to make the changes manually, the details are below:
We have adopted the same versioning strategy as have been adopted by babel, jest and apollo. It's a strategy best suited for ecosystem type tools, which consist of many separately installable features / packages. We think this describes storybook pretty well.
The new package names are:
| old | new |
|---|---|
getstorybook |
@storybook/cli |
@kadira/getstorybook |
@storybook/cli |
@kadira/storybook |
@storybook/react |
@kadira/react-storybook |
@storybook/react |
@kadira/react-native-storybook |
@storybook/react-native |
storyshots |
@storybook/addon-storyshots |
@kadira/storyshots |
@storybook/addon-storyshots |
@kadira/storybook-ui |
@storybook/ui |
@kadira/storybook-addons |
@storybook/addons |
@kadira/storybook-channels |
@storybook/channels |
@kadira/storybook-channel-postmsg |
@storybook/channel-postmessage |
@kadira/storybook-channel-websocket |
@storybook/channel-websocket |
@kadira/storybook-addon-actions |
@storybook/addon-actions |
@kadira/storybook-addon-links |
@storybook/addon-links |
@kadira/storybook-addon-info |
@storybook/addon-info |
@kadira/storybook-addon-knobs |
@storybook/addon-knobs |
@kadira/storybook-addon-notes |
@storybook/addon-notes |
@kadira/storybook-addon-options |
@storybook/addon-options |
@kadira/storybook-addon-graphql |
@storybook/addon-graphql |
@kadira/react-storybook-decorator-centered |
@storybook/addon-centered |
If your codebase is small, it's probably doable to just replace them by hand. (in your codebase and in package.json).
But if you have a lot of occurrences in your codebase, you can use a codemod we created for you.
A codemod makes automatic changed to your app's code.
You have to change your package.json, prune old and install new dependencies by hand.
npm prune will remove all dependencies from node_modules which are no longer referenced in package.json.
We used to ship 2 addons with every single installation of storybook: actions and links. But in practice not everyone is using them, so we decided to deprecate this and in the future they will be completely removed. If you use @storybook/react/addons you will get a deprecation warning.
If you are using these addons, migrating is simple:
- add the addons you use to your
package.json. - update your code:
change
addons.jslike so:changeimport '@storybook/addon-actions/register'; import '@storybook/addon-links/register';
x.story.jslike so:import React from 'react'; import { storiesOf } from '@storybook/react'; import { action } from '@storybook/addon-actions'; import { linkTo } from '@storybook/addon-links';