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

@plexure/react

v0.1.0

Published

React bindings for plexure, a drifting field of points connected by lines, reacting to the pointer.

Readme

@plexure/react

React bindings for plexure, a drifting field of points connected by lines, reacting to the pointer.

import { Plexure } from '@plexure/react';

<Plexure cursor={{ color: '#7fd4c1' }} />

The wrapper is under 1 kB and adds no behaviour of its own. Every option is the engine's PlexureOptions, covered in the engine's README.

Install

npm install @plexure/react plexure

plexure is a peer dependency, so you and the wrapper share one copy. Two copies would each run their own animation loop.

Use

import { Plexure } from '@plexure/react';

function Hero() {
  return (
    <section style={{ position: 'relative' }}>
      <Plexure
        className="absolute-fill" /* position the host div yourself */
        star={{ color: 'var(--ink)' }}
        link={{ distance: 130 }}
        cursor={{ color: '#7fd4c1' }}
      />
      <h1>Your content</h1>
    </section>
  );
}

<Plexure /> renders a host div and mounts a field into it. Props are the engine's options. Change one and it applies through setOptions, so nothing remounts. That makes intensity cheap to drive from scroll.

Unmounting destroys the field and returns every listener.

The handle

A ref gives you the engine handle:

const field = useRef<PlexureInstance>(null);

<Plexure ref={field} />;

field.current?.pause();
field.current?.setOptions({ count: null });

In your tests

Rendering <Plexure /> in jsdom is a non-event. The engine sees it cannot paint and hands back an inert handle. Nothing throws, and nothing needs mocking. StrictMode's double mount leaves one canvas, not two.

License

MIT © Jordan Cowan