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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@salvadorlimones/sparkle

v1.0.7

Published

A package that makes your code sparkle

Downloads

19

Readme

✨ sparkle

A delightful React component that adds animated sparkle effects to your content. Perfect for making your UI elements shine!

Installation

npm install sparkle

Usage

import { Sparkle } from 'sparkle';

function App() {
  return (
    <div>
      <h1>
        <Sparkle>Welcome!</Sparkle>
      </h1>
      
      <p>
        This text has <Sparkle count={20} color="#FF6B9D">sparkles</Sparkle> around it!
      </p>
    </div>
  );
}

Props

| Prop | Type | Default | Description | |------|------|---------|-------------| | children | React.ReactNode | required | The content to wrap with sparkles | | count | number | 12 | Number of sparkle particles | | color | string | '#FFD700' | Color of the sparkles (hex, rgb, or named color) | | size | number | 4 | Size of each sparkle in pixels |

Examples

Basic Usage

<Sparkle>Hello World!</Sparkle>

Custom Count

<Sparkle count={30}>More sparkles!</Sparkle>

Custom Color

<Sparkle color="#FF6B9D">Pink sparkles</Sparkle>
<Sparkle color="rgb(100, 200, 255)">Blue sparkles</Sparkle>
<Sparkle color="purple">Purple sparkles</Sparkle>

Custom Size

<Sparkle size={8}>Bigger sparkles</Sparkle>

Combined Customization

<Sparkle count={25} color="#00FF88" size={6}>
  Fully customized sparkles!
</Sparkle>

With Buttons

<button>
  <Sparkle count={15} color="#FFD700">
    Click me! ✨
  </Sparkle>
</button>

With Headings

<h1>
  <Sparkle count={20} color="#FF6B9D" size={5}>
    Special Announcement
  </Sparkle>
</h1>

Requirements

  • React >= 16.8.0
  • React DOM >= 16.8.0

Documentation

For a general guide on how to create an npm package and set up the versioning/publish workflow (with this repo as an example), see DOCUMENTATION.md.

Development Workflow

This project uses Changesets for version management and automated publishing.

Making Changes

  1. Create a feature branch:

    git checkout -b feature/your-feature-name
  2. Make your changes and test them locally:

    npm run lint    # Type check
    npm run build   # Build the package
  3. Create a changeset before merging:

    npx changeset
    • Select the version bump type (patch, minor, or major)
    • Write a description of your changes
    • This creates a file in .changeset/ directory
  4. Commit and push:

    git add .
    git commit -m "Your commit message"
    git push origin feature/your-feature-name
  5. Open a Pull Request on GitHub

Publishing Process

When your PR is merged to main:

  1. CI runs automatically - Lints and builds your code
  2. Publish workflow detects changesets - If changesets exist, it creates a "Version Packages" PR
  3. Review and merge the Version PR - This will:
    • Bump the version in package.json
    • Update CHANGELOG.md
    • Create a git tag
    • Automatically publish to npm

First Time Setup (for maintainers)

To enable automatic publishing, set up the NPM_TOKEN secret in GitHub:

  1. Go to your npm account: https://www.npmjs.com/settings/YOUR_USERNAME/tokens
  2. Create a new token (type: "Automation")
  3. In your GitHub repo: Settings → Secrets and variables → Actions
  4. Add a new secret named NPM_TOKEN with your npm token

License

MIT

Contributing

Contributions are welcome! Feel free to open an issue or submit a pull request.