Gathering detailed insights and metrics for svelte-range-slider-pips
Gathering detailed insights and metrics for svelte-range-slider-pips
Multi-Thumb, Accessible, Beautiful Range Slider with Pips
Installations
npm install svelte-range-slider-pipsDeveloper Guide
BETA
Typescript
Yes
Module System
ESM
Node Version
22.14.0
NPM Version
10.9.2
Releases
17
Languages
6
TypeScript
Svelte
CSS
JavaScript
HTML
Vue
TypeScript (62.62%)
Svelte (27.69%)
CSS (7.14%)
JavaScript (1.37%)
HTML (0.81%)
Vue (0.38%)
Developer
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MPL-2.0 License
495 Stars
269 Commits
45 Forks
5 Watchers
2 Branches
8 Contributors
Updated on Jul 12, 2025
Maintainers
1
Package Meta Information
Latest Version
4.0.7
Package Id
svelte-range-slider-pips@4.0.7
Unpacked Size
448.01 kB
Size
94.69 kB
File Count
21
NPM Version
10.9.2
Node Version
22.14.0
Published on
Jun 30, 2025
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Peer Dependencies
1
Dev Dependencies
36
@playwright/test@rollup/plugin-commonjs@rollup/plugin-node-resolve@rollup/plugin-terser@rollup/plugin-typescript@sveltejs/adapter-auto@sveltejs/kit@sveltejs/package@sveltejs/vite-plugin-svelte@tailwindcss/typography@tailwindcss/vite@testing-library/jest-dom@testing-library/svelte@types/node@types/testing-library__jest-domdaisyuifeather-iconsglobbyjsdompre-commitprettierprettier-plugin-sveltepublintrolluprollup-plugin-css-onlyrollup-plugin-deleterollup-plugin-filesizerollup-plugin-sveltesveltesvelte-checksvelte-preprocesstailwindcsstslibtypescriptvitevitest
Svelte Range Slider v4
A reactive, accessible, multi-thumb, range slider with the ability to display "pips" or "notches" along the range.
Importable as a svelte-component, or able to be used directly in any javascript application / framework.
| 📔🔍 | Docs | Full Documentation & Examples |
|---|---|---|
| 📝⚙ | REPL | Svelte component demo |
| ❤✒ | Codepen | Plain JS component demo |
Features
- ✨ fully customisable
- ♿ accessible
- 👍🏽 multi-thumb
- 🎚 ranges
- 🏷 floating labels
- 📏 ruler values (pips)
- 🏷 labels for values
- 🧮 step function
- 🖍 formatter
- 🎭 animated
- 🖋 css variables
Install
Open your project and use the command line to install the package;
1yarn add svelte-range-slider-pips --dev # or 2npm install svelte-range-slider-pips --save-dev # if you prefer npm
Usage
Upgrading from v3 -> v4
Note: Please read the upgrade guide for details, as there's some changes which might break your styling/ui.
In a svelte 4 project
Assuming you have a Svelte app up and running;
1<script> 2 import RangeSlider from 'svelte-range-slider-pips'; 3</script> 4 5<RangeSlider values={[50]} pips />
-
see test folder for examples of usage with Svelte 4
-
or Svelte 5
In a svelte 5 project
Svelte 5 works almost exactly the same as Svelte 4.
⚠ Note: Runes Mode -- specifically $state() -- has some issues when binding with an <input /> element.
My suggestion would be to use legacy mode if you can (not runes), or read this issue for a workaround.
In a svelte 3 project
⚠ Version 3 of Range Slider Pips is not compatible with Svelte 3. see below
As a regular JS file
If you're not building a svelte-app, you can use the /dist/
version of the script /dist/svelte-range-slider-pips.js and include it
with a regular <script> tag.
This should even work with jQuery.
1<!-- in the <head> of your html --> 2<script src="./js/vendor/svelte-range-slider-pips.js" /> 3 4<!-- in the <body> of your html --> 5<div id="my-slider"></div> 6 7<script> 8 // this script will be run when the DOM is ready 9 // and the slider is initialised 10 document.addEventListener('DOMContentLoaded', () => { 11 var mySlider = new RangeSliderPips({ 12 target: document.querySelector('#my-slider'), 13 props: { values: [50], pips: true } 14 }); 15 }); 16</script>
- see examples of usage with Vanilla JS
- or running with jQuery
As a JS module, or with Vue & React
If you're building a bleeding-edge JS application (maybe Vue or React), you might
want to use js imports (import)
1import RangeSlider from './node_modules/svelte-range-slider-pips/dist/svelte-range-slider-pips.mjs';
2
3var mySlider = new RangeSlider({
4 target: node, // js reference to a DOM element
5 props: { values: [50], pips: true }
6});- see examples of usage with ES modules
- or usage with VueJS
- or importing with ReactJS
Props (options)
Slider props
| prop | type | default | description |
|---|---|---|---|
| value | Number | 50 | Value to apply on the slider. |
| values | Array | [50] | Array of values to apply on the slider. Multiple values creates multiple handles. (note: A slider with range property set can only have two values max) |
| min | Number | 0 | Minimum value for the slider (should be < max) |
| max | Number | 100 | Maximum value for the slider (should be > min) |
| step | Number | 1 | Every nth value to allow handle to stop at (should be a positive value) |
| range | Boolean/String | false | Whether to style as a range picker. Use range='min' or range='max' for min/max variants |
| pushy | Boolean | false | If range is true, then this boolean decides if one handle will push the other along |
| draggy | Boolean | false | If range is true, enables dragging the range area between handles |
| rangeGapMin | Number | 0 | If range is true, sets the minimum allowed distance between handles |
| rangeGapMax | Number | Infinity | If range is true, sets the maximum allowed distance between handles |
| float | Boolean | false | Set true to add a floating label above focussed handles |
| rangeFloat | Boolean | false | If range is true, shows the range values between handles |
| vertical | Boolean | false | Make the slider render vertically (lower value on bottom) |
| pips | Boolean | false | Whether to show pips/notches on the slider |
| pipstep | Number | 1/10/20 | Every nth step to show a pip for. This has multiple defaults depending on values property |
| first | Boolean/String | false | Whether to show a pip or label for the first value on slider. Use first='label' to show a label value |
| last | Boolean/String | false | Whether to show a pip or label for the last value on slider. Use last='label' to show a label value |
| rest | Boolean/String | false | Whether to show a pip or label for all other values. Use rest='label' to show a label value |
| all | Boolean/String | false | Whether to show a pip or label for all values. Same as combining first, last and rest. Use all='label' to show a label value |
| prefix | String | "" | A string to prefix to all displayed values |
| suffix | String | "" | A string to suffix to all displayed values |
| limits | Array | [0, 100] | An array of two numbers to set a limit on the handles. This overrides min and max if set, while still using them for the range display. |
| reversed | Boolean | false | Reverse the orientation of min/max |
| hoverable | Boolean | true | Whether hover styles are enabled for both handles and pips/values |
| disabled | Boolean | false | Determine if the slider is disabled, or enabled (only disables interactions, and events) |
| id | String | "" | Give the slider a unique ID for use in styling |
| class | String | "" | Add custom CSS classes to the slider |
| style | String | undefined | Pass CSS variables or style declarations directly to the slider |
| darkmode | False/"auto"/"force" | false | Set to "auto" to automatically detect the system's dark mode, or "light" or "dark" to force a specific mode |
| ariaLabels | Array | [] | Array of strings to use for the aria-label attribute on the handles. |
| formatter | Function | (v,i,p) => v | A function to re-format values before they are displayed (v = value, i = pip index, p = percent) |
| handleFormatter | Function | formatter | A function to re-format values on the handle/float before they are displayed. Defaults to the same function given to the formatter property (v = value, i = handle index, p = percent) |
| rangeFormatter | Function | null | A function to re-format range float values (v1 = first value, v2 = second value, p1 = first percent, p2 = second percent) |
| spring | Boolean | true | Whether to enable spring animations on handles |
| springValues | Object | { stiffness: 0.15, damping: 0.4 } | Svelte spring physics object to change the behaviour of the handle when moving |
| precision | Number | 2 | Precision of the values for fixing floating errors |
| slider | Element | undefined | DOM reference for binding to the main <div /> of the component (bind:slider='ref') |
📔🔍 | Documentation for Options
Slider events (dispatched)
| event | example | event.detail | description |
|---|---|---|---|
| start | on:start={(e) => { ... }} | { activeHandle: Integer, value: Float, values: Float[] } | Event fired when the user begins interaction with the slider |
| change | on:change={(e) => { ... }} | { activeHandle: Integer, startValue: Float / Float[], previousValue: Float / Float[], value: Float, values: Float[] } | Event fired when the user changes the value; returns the previous value, also |
| stop | on:stop={(e) => { ... }} | { activeHandle: Integer, startValue: Float / Float[], value: Float, values: Float[] } | Event fired when the user stops interacting with slider; returns the beginning value, also |
Styling
Styling should mostly be done with CSS.
There's a bunch of css variables for controlling the colors of the elements.
And the slider is fluid horizontally, with the size of things controlled by font-size. So you may change the font-size on the .rangeSlider base
element to change the scale of everything.
If you require more fine control of the widths, heights, etc, then you may override the default css. This can be easier by using the id prop
to give your slider a unique id.
Values of labels can be styled with CSS, and the format can be modified with the formatter() function prop. And animation of the handles is
controlled by the springValues object prop.
📔🔍 | Documentation for Styling
Note: In
v4, most CSS class names have been prefixed withrsto prevent conflicts with generic CSS frameworks like DaisyUI or UnoCSS. See the upgrade guide for details.
Contribute
I am very happy to accept;
- 🌟 suggestions/requests for new features or changes
- 🛠 pull-requests for bug fixes, or issue resolution
- 📝 new recipes/examples for the docs site
- 🧪 help with adding more tests
But please read the CONTRIBUTING.md first.
Notes
Svelte 3
⚠ Because of new code added in Range Slider v3, it is incompatible with Svelte version 3.
If you are unable to upgrade your project to Svelte4/Svelte5, then I suggest looking for Svelte-Range-Slider-Pips version 2.3.1 which
will not be upgraded, but it's still pretty robust. You can install it like so;
1yarn add svelte-range-slider-pips@2.3.1 --dev # or 2npm install svelte-range-slider-pips@2.3.1 --save-dev # if you prefer npm
Support / Tip
I'd be super excited if you find this project useful and wish to donate a small amount for my efforts!
 |  | £1 GBP Tip |
|---|---|---|
|  | £5 GBP Tip |
|  | £10 GBP Tip |
No vulnerabilities found.
Reason
25 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE-MPL-2.0:0
- Info: FSF or OSI recognized license: Mozilla Public License 2.0: LICENSE-MPL-2.0:0
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/tests.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/simeydotme/svelte-range-slider-pips/tests.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/tests.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/simeydotme/svelte-range-slider-pips/tests.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/tests.yml:41: update your workflow using https://app.stepsecurity.io/secureworkflow/simeydotme/svelte-range-slider-pips/tests.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/tests.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/simeydotme/svelte-range-slider-pips/tests.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/tests.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/simeydotme/svelte-range-slider-pips/tests.yml/main?enable=pin
- Info: 0 out of 5 GitHub-owned GitHubAction dependencies pinned
- Info: 2 out of 2 npmCommand dependencies pinned
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/tests.yml:1
- Info: no jobLevel write permissions found
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Reason
39 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8
- Warn: Project is vulnerable to: GHSA-mh2x-fcqh-fmqv
- Warn: Project is vulnerable to: GHSA-rjjv-87mx-6x3h
- Warn: Project is vulnerable to: GHSA-6q87-84jw-cjhp
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-67mh-4wv8-2f99
- Warn: Project is vulnerable to: GHSA-78xj-cgh5-2h22
- Warn: Project is vulnerable to: GHSA-2p57-rm9w-gvfp
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-f5x3-32g6-xq36
- Warn: Project is vulnerable to: GHSA-x574-m823-4x7w
- Warn: Project is vulnerable to: GHSA-4r4m-qw57-chr8
- Warn: Project is vulnerable to: GHSA-xcj6-pq6g-qj4x
- Warn: Project is vulnerable to: GHSA-356w-63v5-8wf4
- Warn: Project is vulnerable to: GHSA-859w-5945-r5v3
- Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j
- Warn: Project is vulnerable to: GHSA-qwcr-r2fm-qrc7
- Warn: Project is vulnerable to: GHSA-qw6h-vgh9-j6wx
- Warn: Project is vulnerable to: GHSA-c7qv-q95q-8v27
- Warn: Project is vulnerable to: GHSA-4www-5p9h-95mh
- Warn: Project is vulnerable to: GHSA-9gqv-wp59-fq42
- Warn: Project is vulnerable to: GHSA-mwcw-c2x4-8c55
- Warn: Project is vulnerable to: GHSA-rp65-9cf3-cjxr
- Warn: Project is vulnerable to: GHSA-rhx6-c78j-4q9w
- Warn: Project is vulnerable to: GHSA-7fh5-64p2-3v2j
- Warn: Project is vulnerable to: GHSA-gcx4-mw62-g8wm
- Warn: Project is vulnerable to: GHSA-m6fv-jmcg-4jfg
- Warn: Project is vulnerable to: GHSA-cm22-4g7w-348p
- Warn: Project is vulnerable to: GHSA-4v9v-hfq4-rm2v
- Warn: Project is vulnerable to: GHSA-9jgg-88mc-972h
- Warn: Project is vulnerable to: GHSA-8266-84wp-wv5c
- Warn: Project is vulnerable to: GHSA-8jhw-289h-jh2g
- Warn: Project is vulnerable to: GHSA-64vr-g452-qvp3
- Warn: Project is vulnerable to: GHSA-9cwx-2883-4wfx
- Warn: Project is vulnerable to: GHSA-vg6x-rcgg-rjx6
- Warn: Project is vulnerable to: GHSA-g3ch-rx76-35fx
Score
3.6
/10
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More