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-input-component

v0.2.0

Published

react-input-component

Downloads

23

Readme

react-input-component

CircleCI Build Status

🚀 A better alternative to react built-in input components

Motivations

  1. Before use built-in react inputs, you may need to know what the hell are controlled and uncontrolled inputs
  2. Controlled input has a bug
  3. Controlled input is slow
  4. Uncontrolled input is not powerful

So I created this module to avoid the problems above.

Installation

yarn add react-input-component

Usages

Just like built-in input components, but no defaultValue or defaultChecked prop.

Example
import React from 'react';
import { Input } from 'react-input-component';

export default () =>
    <Input value="feel free to type here..." />
Components
  • Input
  • TextArea
  • Select

Notes

  • All styles are the same with react built-in inputs
  • All react built-in inputs' props are supported, except defaultValue and defaultChecked
  • To get the DOM, use findDOMNode(input) or input.dom. (This input refs to an Input instance, like <Input ref="input" />)
  • Form data (value or checked) would be handled by the DOM itself.
  • Form data could also be changed by passing new value prop to component.

Caveat

If the new value prop is equal to the prev value prop, form data would not be updated, even if form data is not equal to the value prop.

import React, { Component } from 'react';
import { render, findDOMNode } from 'react-dom';
import { Input } from 'react-input-component';

class Bad extends Component {
    state = { value: 'a' };

    componentDidMount() {
        findDOMNode(this).value = 'b'; // Simulate user typing

        // Try to reset `value` to "a", but failed
        // Because the new `value` prop is equal to the prev `value` prop
        this.setState({ value: 'a' }); // => BAD
    }

    render() {
        return (<Input {...this.state} />);
    }
}

render(<Bad />, document.getElementById('root'));

To resolve this problem, you could change the DOM value directly, or add a special updateKey prop.

updateKey helps Input component to decide to update. If updateKey changes, form data changes.

import React, { Component } from 'react';
import { render, findDOMNode } from 'react-dom';
import { Input } from 'react-input-component';

class Good extends Component {
    state = { value: 'a' };

    componentDidMount() {
        findDOMNode(this).value = 'b'; // Simulate user typing

        // Try to reset `value` to "a"
        // Adding a new `updateKey` to force upate
        this.setState({ value: 'a', updateKey: Math.random() }); // => GOOD
    }

    render() {
        return (<Input {...this.state} />);
    }
}

render(<Good />, document.getElementById('root'));

License

MIT © Cap32