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

@myxplor/forms

v0.10.18

Published

A standard way to render our form inputs, textareas, and submit buttons. The best way to get a feel of how these components work is via storybook.

Downloads

16

Readme

Forms

A standard way to render our form inputs, textareas, and submit buttons. The best way to get a feel of how these components work is via storybook.

FormInput, FormPassword and FormTextArea all share the below props

  • name - name of input. required
  • onChange - callback function when input changes. required
  • required - if a value is required, for browser clientside validation. Also adds "*" after label text
  • label - human readable text displayed above input. Optional, if no value provided, uses name
  • value - the default value of the input
  • hint - hint text, display below the input
  • errors - an array of errors to be displayed. If this provided, the input will turn red.
  • loading - if the form is loading/submitting. If is loading, input becomes readonly, and errors are reset. (so that hint text is displayed again)
  • maxLength - displays a countdown timer of how many chars remaining
  • autoFocus - if the input should be automatically focused. Only if the user agent is not a mobile

Note: FormSubmit, has its' own set of props.


  <FormInput 
    required={true} 
    name="email"
    label="First Name"
    value="Thomas"
    autoFocus="true"
    onChange={this.handleChange}
  />

With errors

screen shot 2018-03-09 at 5 01 06 pm

Pass the errors props an array of errors


  <FormInput 
    required={true} 
    name="first_name"
    label="First Name"
    value="Thomas"
    errors={[
      "This needs to be filled out"
    ]}
    onChange={this.handleChange}
  />

Note: in your errors, if you pass an object with a key of title it will be rendered in bold.


  <FormInput 
    name="first_name"
    label="First Name"
    value="Thomas"
    errors={
      [
        { "title": "Opps" },
        "This is terrible"
      ]
    }
    onChange={this.handleChange}
  />

screen shot 2018-03-09 at 5 18 38 pm