Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

react-component-playground

Package Overview
Dependencies
Maintainers
2
Versions
39
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

react-component-playground

Isolated loader for React components

  • 1.0.0
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
8
decreased by-61.9%
Maintainers
2
Weekly downloads
 
Created
Source

react-component-playground

UI for interacting with your components and their respective fixtures.

Full disclosure: CP is a large component that could be split into more modular pieces.

Right now it embodies the following 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.

  • TODO: Move into separate ComponentList component.
  1. The CodeMirror fixture editor, JSON format.
  • 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.
  • TODO: Move into separate Editor component.
  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. Component loader. Render selected component with selected fixture contents.
  • Fixture is extended by user input from the editor and updates from state listeners.
  1. Proxies. Composable middleware between CP and preview component.
  • They can add extra markup around the preview component.
  • They can alter fixture contents before reaching the preview component.
  • They can hook into the preview component's callback ref to obtain its instance.
  • They receive an onFixtureUpdate handler that enables them to update current fixture contents from alternative sources (e.g. Redux store)

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

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

FAQs

Package last updated on 04 Nov 2016

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc