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

react-cosmos-playground-hs

v4.0.0

Published

Dev tool for creating reusable React components

Downloads

2

Readme

react-cosmos-playground

UI for interacting with your components and their respective fixtures.

Parts:

  1. The fixed header with the home button, alongside the toggle editor and full-screen buttons.

  2. The list of components/fixtures with fuzzy search functionality and navigation between them. See FixtureList.

  3. The CodeMirror fixture editor, JSON format. See FixtureEditor.

  • It serializes the fixture and only displays the serializable parts, invisibly storing the rest. On user changes, the editor content is parsed and merged with the unserializable rest to form the updated fixture to render.
  • It keeps a copy of the editor contents since they were last JSON valid to merge into the fixture contents (used to render component), while user is typing and possibly making syntax errors along the way.
  • The editor ignores fixture updates when focused, giving priority to user input over component state changes.
  1. A draggable split pane between the editor and the component preview.
  • The desired split position is persisted using localStorage.
  • It automatically chooses a portrait/landscape orientation to best serve the width/height ratio of the window.
  1. Communication with Component loader, which renders selected component with selected fixture contents.

Finally, here is an example of the components and fixtures props, used to pass the user components and fixtures:

fixtures: {
  ComponentOne: {
    normal: {
      component: require('./components/ComponentOne'),
      fooProp: 'bar'
    },
    paused: {
      component: require('./components/ComponentOne'),
      fooProp: 'bar',
      state: {
        paused: true
      }
    }
  },
  ComponentTwo: {
    //...
  }
};