svelte-range-slider-pips
Advanced tools
Comparing version 1.3.1 to 1.4.0
@@ -40,3 +40,3 @@ { | ||
], | ||
"version": "1.3.1", | ||
"version": "1.4.0", | ||
"description": "Multi-Thumb, Accessible, Beautiful Range Slider with Pips", | ||
@@ -46,4 +46,4 @@ "repository": "https://github.com/simeydotme/svelte-range-slider-pips", | ||
"author": "Simon Goellner <simey.me@gmail.com>", | ||
"license": "MIT", | ||
"license": "MPL-2.0", | ||
"private": false | ||
} |
@@ -24,2 +24,4 @@ | ||
### in a svelte project | ||
Assuming you have a Svelte app up and running; | ||
@@ -35,2 +37,33 @@ | ||
### as a regular JS file | ||
If you're using a different framework, or none, you can use the [`/dist/` | ||
version of the script `/dist/svelte-range-slider-pips.js`](dist/svelte-range-slider-pips.js) and include it | ||
either with a regular `<script>` tag, or by using js imports (`import`) | ||
```html | ||
<script src="./js/vendor/svelte-range-slider-pips.js" /> | ||
<div id="my-slider"></div> | ||
<script> | ||
var mySlider = new RangeSliderPips({ | ||
target: document.getElementById("my-slider"), | ||
props: { /* props as js object */ } | ||
}); | ||
</script> | ||
``` | ||
### as a JS module | ||
```js | ||
import RangeSlider from "./node_modules/svelte-range-slider-pips/dist/svelte-range-slider-pips.mjs"; | ||
var mySlider = new RangeSlider({ | ||
target: node, // js reference to a DOM element | ||
props: { /* props as js object */ } | ||
}); | ||
``` | ||
--- | ||
## props (options) | ||
@@ -64,9 +97,9 @@ ### slider props | ||
I am very happy to accept; | ||
- suggestions/requests for new features or changes with examples of how they would be useful | ||
- pull-requests for bug fixes, or issue resolution | ||
- help with creating a proper test-suite | ||
- 🌟 suggestions/requests for new features or changes with examples of how they would be useful | ||
- 🛠 pull-requests for bug fixes, or issue resolution | ||
- 🧪 help with creating a proper test-suite | ||
When making changes/edits to the code you should use the `/test/` folder and check the Readme.md in there | ||
**When making changes/edits to the code you should use the `/test/` folder** and check the [README.md](test/README.md) in there | ||
to help with testing all the functionality. I don't have real tests set up, and would appreciate anyone's | ||
help who knows how to accomplish that. | ||
Sorry, the diff of this file is too big to display
Sorry, the diff of this file is not supported yet
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Copyleft License
License(Experimental) Copyleft license information was found.
Found 1 instance in 1 package
Non-permissive License
License(Experimental) A license not known to be considered permissive was found.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
184275
8
3916
103
2
70