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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ztolley/storybook-react-input-state

v1.0.0

Published

State wrapper for form components in react storybook stories

Readme

@ztolley/storybook-react-input-state

This Storybook JS component allows you to create storybooks that present functional Form components that would normally need some kind of stateful container. So if you created a functional input component you can try it out by simplying wrapping it in this component. So how easy is it to use? This easy:

<State>
  <Input name="colour" value="Red" />
</State>

There are already a few plugins and components to help with state in Storybook, but they provide more advanced functionality and do not work well with the storybook-info addon. This plugin attempts to require zero configuration while keeping the output clean and is specifically designed to wrap form input components, using the name property as the state key.

Below is an example story using the component:

Input.stories.js
----------------
import React from 'react'
import { storiesOf } from '@storybook/react'
import State from '@ztolley/storybook-react-input-state'

import Input from './Input'

const stories = storiesOf('Input', module)

stories.add('Input', () => (
  <form>
    <State>
      <Input name="user" label="User" type="text" value="fred" />
      <Input name="colour" label="Colour" type="text" value="" />
    </State>
  </form>
))

If you wish to add add the storybook-info the code required would be something like:

.storybook/config.js
--------------------
import { withInfo } from '@storybook/addon-info'
import { addDecorator, configure } from '@storybook/react'

addDecorator(withInfo)

...


Input.stories.js
----------------
import React from 'react'
import { storiesOf } from '@storybook/react'
import State from '@ztolley/storybook-react-input-state'

import Input from './index'

const stories = storiesOf('Input', module)
stories.addParameters({
  info: { inline: true, header: false, propTablesExclude: [State] },
})

stories.add('Input', () => (
  <State>
    <Input name="user" label="User" type="text" value="fred" />
  </State>
))

The result will be a Storybook story that shows the component in action, example code (only wrapping it in a State component) and a property table.

Finally, if you add your own onChange property to an input that method will still get called in addition to the state listening for changes.

If you have any questions, then either log them in the issue tracker or tweet @ztolley.