Gathering detailed insights and metrics for vue-sparkles
Gathering detailed insights and metrics for vue-sparkles
Gathering detailed insights and metrics for vue-sparkles
Gathering detailed insights and metrics for vue-sparkles
vue-json-schema-form
Generate forms from your JSON schemas! :sparkles:
notification-quark
This quark is a simple vue plugin with notification component and added sparkles in the form of a store that handles the behaviour. <br/> It is a simple notification system that can be used to display messages to the user on plethora events happening in
npm install vue-sparkles
Typescript
Module System
Min. Node Version
Node Version
NPM Version
JavaScript (68.17%)
Vue (31.83%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
10 Stars
20 Commits
2 Forks
1 Watchers
14 Branches
2 Contributors
Updated on May 07, 2024
Latest Version
1.1.0
Package Id
vue-sparkles@1.1.0
Unpacked Size
38.83 kB
Size
9.48 kB
File Count
7
NPM Version
6.14.12
Node Version
12.22.1
Cumulative downloads
Total Downloads
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
A Vue component making things a little sparklier
Vue Sparkles is the Vue.JS variant of Josh W Comeau's animated sparkles for React. I took a couple of different approaches to the idea than he did. And I had to, since this is Vue and not React, of course :) It is essentially the same though.
It could look like this in action
easy, in your command line of choice:
npm install vue-sparkles --save
You have it installed. Now we just have to import it: in your main.js import the component like this
import VueSparkles from 'vue-sparkles';
And then we have to tell Vue to use it.
Vue.use(VueSparkles);
Just wrap your soon-to-be sparkly element in a <VueSparkles> tag. That could look as follows
<VueSparkles><h1>What a great looking Header this is</h1></VueSparkles>
Or like so
<VueSparkles><img src="@/assets/img/some-image.png" alt="A sparkling image" /></VueSparkles>
You want to get more into customization? No problem!
You can pass a color prop to apply a custom color. Only an HSL style of colors work though. If you don't pass any color prop all sparkles will use the default of hsl(50deg, 100%, 50%)
<VueSparkles
color="hsl(0deg, 100%, 50%)">
<h1>What a great looking Header this is</h1>
</VueSparkles>
Alright, alright, I understand. You are thirsty now. You want more. No problem. Multiple Colors! To achieve that, I find it easiest to bind the color prop to a variable. Said var could look like this
color: [
{
h: '0',
s: '100',
l: '50'
},
{
h: '50',
s: '100',
l: '50'
}
]
This will give you a nice rainbowy effect of colors ranging from red to yellow for example. Notice how I only changed the hue and left the saturation and luminance the same. I would urge you to do the same if you don't intentionally aim for a different effect.
You can also use different paths. If you don't pass a path object, all sparkles will use the default star sparkle created by Josh Comeau.
There is a restriction however! Since you are only changing the path, you won't be able to change stuff such as viewBox or stroke. That means you will be limited to filled SVGs, no outline icons here. Also, the viewBox is 0 0 160 160
, so if your path doesn't respect that it is either cut on the viewBox borders or it will be so small you can't see it.
So, this should be pretty self-explanatory. For a single path you just have to pass the path-string through the path prop. That could look like this:
<VueSparkles
path="...">
<h1>What a great looking Header this is</h1>
</VueSparkles>
For multiple paths, just bind the path-prop to an array containing the paths.
color
or path
prop
If you think this can be optimized in any way, please feel free to do so, this is open source after all :)
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
dependency not pinned by hash detected -- score normalized to 3
Details
Reason
project is archived
Details
Reason
Found 1/18 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
license file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
37 existing vulnerabilities detected
Details
Score
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