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

@tsparticles/particles

v4.1.1

Published

Easily create highly customizable particle animations and use them as animated backgrounds for your website. Ready to use components available also for React, Vue.js (2.x and 3.x), Angular, Svelte, jQuery, Preact, Riot.js, Inferno.

Readme

banner

tsParticles Particles Bundle

jsDelivr npmjs npmjs GitHub Sponsors

tsParticles particles bundle to create simple particle effects with a focused API.

Included Packages

Exposed API

The package API is centered on particles.

import { particles } from "@tsparticles/particles";

// Main API
const instance = await particles();
const byId = await particles("canvas-id", options);
const byOptions = await particles(options);

// Extra helpers
await particles.init();
const custom = await particles.create(canvas, options);

console.log(particles.version);

@tsparticles/particles does not expose tsParticles from its main entrypoint. If you need direct engine APIs, import them from @tsparticles/engine.

Installation

pnpm add @tsparticles/particles

Lazy entrypoint (loads dependencies on demand):

import { particles } from "@tsparticles/particles/lazy";

How to use it

import { particles } from "@tsparticles/particles";

const instance = await particles({
  count: 120,
  color: "#00f",
  links: true,
  linksColor: "#0ff",
  linksLength: 140,
  radius: 4,
  shape: ["circle", "square"],
});

instance?.pause();
instance?.play();
instance?.stop();

Custom canvas via particles.create

import { particles } from "@tsparticles/particles";

const canvas = document.getElementById("my-canvas") as HTMLCanvasElement;
await particles.create(canvas, { links: true });

Options

Main options (shallow overview):

  • count Number: particles amount (default: 80)
  • radius Number or RangeValue: particle radius (default: 3)
  • links Boolean: enable links between particles
  • linksLength Number: maximum link distance
  • speed Number or RangeValue: particle movement speed
  • collisions Boolean: enable particle collisions
  • opacity Number: particle opacity
  • shape String or Array<String>: particle shape type(s)
  • color String: particle color
  • linksColor String: link color

Returned instance methods

The resolved ParticlesInstance exposes:

  • pause()
  • play()
  • stop()

Common pitfalls

  • Calling particles before scripts are loaded in CDN usage
  • Assuming tsParticles is exported by @tsparticles/particles main entrypoint
  • Reusing the same id unintentionally (the package caches instances by id)

Related docs