npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@forbeslindesay/addon-actions

v5.1.0-alpha.29

Published

Action Logger addon for storybook

Downloads

4

Readme

Storybook Addon Actions

Storybook Addon Actions can be used to display data received by event handlers in Storybook.

Framework Support

Screenshot

Getting Started

Install:

npm i -D @storybook/addon-actions

Then, add following content to .storybook/addons.js

import '@storybook/addon-actions/register';

Import the action function and use it to create actions handlers. When creating action handlers, provide a name to make it easier to identify.

Note: Make sure NOT to use reserved words as function names. issues#29

import { storiesOf } from '@storybook/react';
import { action, configureActions } from '@storybook/addon-actions';

import Button from './button';

storiesOf('Button', module).add('default view', () => (
  <Button onClick={action('button-click')}>Hello World!</Button>
));

Multiple actions

If your story requires multiple actions, it may be convenient to use actions to create many at once:

import { storiesOf } from '@storybook/react';
import { actions } from '@storybook/addon-actions';

import Button from './button';

// This will lead to { onClick: action('onClick'), ... }
const eventsFromNames = actions('onClick', 'onMouseOver');

// This will lead to { onClick: action('clicked'), ... }
const eventsFromObject = actions({ onClick: 'clicked', onMouseOver: 'hovered' });

storiesOf('Button', module)
  .add('default view', () => <Button {...eventsFromNames}>Hello World!</Button>)
  .add('default view, different actions', () => (
    <Button {...eventsFromObject}>Hello World!</Button>
  ));

Action Decorators

If you wish to process action data before sending them over to the logger, you can do it with action decorators.

decorate takes an array of decorator functions. Each decorator function is passed an array of arguments, and should return a new arguments array to use. decorate returns a object with two functions: action and actions, that act like the above, except they log the modified arguments instead of the original arguments.

import { decorate } from '@storybook/addon-actions';

import Button from './button';

const firstArg = decorate([args => args.slice(0, 1)]);

storiesOf('Button', module).add('default view', () => (
  <Button onClick={firstArg.action('button-click')}>Hello World!</Button>
));

Configuration

Arguments which are passed to the action call will have to be serialized while be "transfered" over the channel.

This is not very optimal and can cause lag when large objects are being logged, for this reason it is possible to configure a maximum depth.

The action logger, by default, will log all actions fired during the lifetime of the story. After a while this can make the storybook laggy. As a workaround, you can configure an upper limit to how many actions should be logged.

To apply the configuration globally use the configureActions function in your config.js file.

import { configureActions } from '@storybook/addon-actions';

configureActions({
  depth: 100,
  // Limit the number of items logged into the actions panel
  limit: 20,
})

To apply the configuration per action use:

action('my-action', {
  depth: 5,
})

Available Options

|Name|Type|Description|Default| |---|---|---|---| |depth|Number|Configures the transfered depth of any logged objects.|10| |clearOnStoryChange|Boolean|Flag whether to clear the action logger when switching away from the current story.|true| |limit|Number|Limits the number of items logged in the action logger|50|

withActions decorator

You can define action handles in a declarative way using withActions decorators. It accepts the same arguments as actions Keys have '<eventName> <selector>' format, e.g. 'click .btn'. Selector is optional. This can be used with any framework but is especially useful for @storybook/html.

import { storiesOf } from '@storybook/html';
import { withActions } from '@storybook/addon-actions';

storiesOf('button', module)
  // Log mouseovers on entire story and clicks on .btn
  .addDecorator(withActions('mouseover', 'click .btn'))
  .add('with actions', () => `
    <div>
      Clicks on this button will be logged: <button className="btn" type="button">Button</button>
    </div>
  `);