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

typable-react

v0.0.15

Published

React.js prop-types wrapper for easy extraction to documentation

Downloads

14

Readme

Typable React

Node.js CI

PropTypes for documentation authors.

Typable is a React PropTypes wrapper that allows for easy extraction of your type metadata.

Installation

npm i prop-types typable-react

Usage

Type your components like this instead of using propTypes. This will implicitly apply propTypes

import typed from 'typable-react'

export default function MyComponent({
  name,
  fruitCount,
  fruit
}) {
  return <h1>Hello {name}, I ate {fruitCount} {fruit}</h1>
}

typed(MyComponent, {
  name: {
    type: typed.string,
    required: true,
    description: 'The name to be greeted'
  },
  fruitCount: {
    type: typed.number,
    default: 0,
    description: 'The number of fruit eaten'
  },
  fruit: {
    type: typed.oneOf(['bananas', 'mangoes']),
    default: 'bananas',
    description: 'The number of fruit eaten'
  },
})

When you need to extract the type metadata for documentation, it's all available at MyComponent.types.

console.log(MyComponent.types)
/*
 {
  name: {
    type: 'string',
    required: true,
    description: 'The name to be greeted'
  },
  fruitCount: {
    type: 'number',
    default: 0,
    description: 'The number of fruit eaten'
  },
  fruit: {
    type: { name: 'oneOf', params: ['bananas', 'mangoes'] },
    default: 'bananas',
    description: 'The number of fruit eaten'
  },
 }
*/

and your installed version of prop-types is applied

MyComponent.propTypes = {
  name: PropTypes.string.isRequired,
  fruitCount: PropTypes.number,
  fruit: PropTypes.oneOf(['bananas', 'mangoes'])
}

MyComponent.defaultProps = {
  fruitCount: 0,
  fruit: 'bananas'
}

WHY?

PropTypes is great for regular use but when building components that need to be documented, it does not give any information about the prop types that can be easily extracted into the documentation. Documentation tools currently use react-docgen or similar implementation to extract by reading the entire source file to parse PropTypes syntax. This is not always straightforward to use as it may require raw loading components to be parsed as strings.

LICENSE

typable-react is MIT licensed. Read details