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

v1.0.0

Published

React Component Range is a simple and minimal React input range component

Downloads

37

Readme

react-component-range

npm version Build Status

React Component Range is a simple and minimal React input range component

Install

npm install react-component-range

Usage

import React, { Component } from "react";
import ReactRange from "react-component-range";

class App extends Component {
  onChange = value => {
    console.debug("Value: ", value);
  };

  render() {
    return (
      <ReactRange
        min={0}
        max={100}
        defaultValue={50}
        ariaLabel="Slider to adjust the volume"
        onChange={this.onChange}
      />
    );
  }
}

export default App;

Props

| Name | Type | Default | Description | | -------------- | -------- | ---------- | -------------------------------------------------------------------------------------------------------------------------------------- | | id | string | | The id of the input (range) | | name | string | | The input's name, to identify the input in the data submitted with the form's data | | min | number | 0 | The minimum permitted value | | max | number | 100 | The maximum permitted value | | step | number | 1 | The stepping interval, used both for user interface and validation purposes | | onChange | function | () => {} | The callback action to be performed when the value changes. It returns the current value. | | value | number | | The input's current value | | defaultValue | number | 0 | The input's initial value | | ariaLabel | string | | The accesibility aria-label property of the input | | ariaLabelledby | string | | The accesibility aria-labelledby property of the input | | disabled | boolean | false | A Boolean attribute which is present if the input should be disabled | | required | bollean | false | A Boolean which, if true, indicates that the input must have a value before the form can be submitted | | tabIndex | number | | A numeric value providing guidance to the user agent as to the order in which controls receive focus when the user presses the Tab key |

Contributing

Feel free to submit issues and enhancement requests.

Please refer to each project's style guidelines and guidelines for submitting patches and additions. In general, we follow the "fork-and-pull" Git workflow.

  1. Fork the repo on GitHub
  2. Clone the project to your own machine
  3. Commit changes to your own branch
  4. Push your work back up to your fork
  5. Submit a Pull request so that we can review your changes

NOTE: Be sure to merge the latest from "upstream" before making a pull request!

Future actions

  • Typescript component
  • Write tests for the component
  • Personalization (color and size)