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 🙏

© 2025 – Pkg Stats / Ryan Hefner

input-range-scss

v2.0.1

Published

Sass component for customizing the input range using the native properties of each browser.

Downloads

16,299

Readme

Styling Cross-Browser Compatible Range Inputs with Sass / SCSS

input-range-scss is a Sass component designed to simplify the customization of <input type="range"> elements across all major browsers. It leverages native browser properties while maintaining accessibility and cross-browser compatibility. This library was created for developers and designers looking to create polished, consistent range sliders without sacrificing usability.

Why Use input-range-scss?

  • Customizable: Easily override default styles with Sass variables to match your design system.
  • Cross-Browser Compatibility: Ensures consistent styling across Chrome, Firefox, Safari, Edge, and Internet Explorer.
  • Accessibility: Preserves native accessibility features, ensuring your sliders are usable for all users.
  • Lightweight: Focused on styling only, with no JavaScript dependencies.
  • Modern Sass Features: Uses the latest Sass module system for clean and maintainable code.

Installation

Install the package via NPM:

npm i input-range-scss

Features

  • Predefined variables for effortless customization
  • Support for modern and legacy browsers
  • Built-in mixins for shadows and other effects
  • Modular Sass structure for easy integration

Example

Below is an example of how the library can transform native range inputs into styled sliders:

Input range native and custom on browsers

Usage

To use this library in your project, import it as a Sass module:

@use 'input-range-scss';

Customizing Styles

Override the default styles by passing your own values to the Sass variables using the with keyword:

@use 'input-range-scss' with (
  $track-color: #ff5722,
  $thumb-color: #4caf50,
  $thumb-height: 20px,
  $thumb-width: 20px,
  $track-height: 10px,
);

Available Variables

Here are some of the key variables you can customize:

  • $track-color: The color of the slider track.
  • $thumb-color: The color of the slider thumb.
  • $thumb-height: The height of the slider thumb.
  • $thumb-width: The width of the slider thumb.
  • $track-height: The height of the slider track.
  • $contrast: Adjusts the contrast for hover and active states.

For a complete list of variables, see the source file.

Changelog

To see the change history of this project, check out the changelog.md file.

See Also