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 🙏

© 2024 – Pkg Stats / Ryan Hefner

wiggly

v0.0.3

Published

<div align="center"> <img src="https://raw.githubusercontent.com/rosszurowski/wiggly/HEAD/media/cover.svg" width="300" alt="Wiggly, a React spring library" /> </div>

Downloads

3

Readme

Spring animations in React & Typescript. Zero dependencies and lightweight (2kb). A simple alternative to libraries like framer-motion (~50kB) and react-spring (~20kB).

Usage

Import the useSpring hook, and tag the element you want to animate with the ref property.

import { useSpring } from "wiggly"

function Panel() {
  const [open, setOpen] = useState(false)
  const y = useSpring(0)

  useEffect(() => {
    y.set(120)
  }, [open])

  return <div ref={y.ref} style={{ transform: `translateY(${y})` }} />
}

To animate multiple properties, create multiple springs and combine the refs with the combineRefs helper:

import { useSpring, combineRefs } from "wiggly"

function Ball(props) {
  const x = useSpring(0)
  const y = useSpring(0)

  useEffect(() => {
    x.set(props.x)
    y.set(props.y)
  }, [props])

  return (
    <div
      ref={combineRefs(x.ref, y.ref)}
      style={{ transform: `transform(${x}, ${y})` }}
    />
  )
}

Examples

A few examples of how to use wiggly are in the examples directory.

Motivation

I frequently want to add spring-based animations to React apps, but feel guilty when I see the bundle sizes of existing solutions

  • react-spring is 19.4kB large.
  • framer-motion is 50.9kB. They offer a tree-shaking guide, but it doesn't make a huge difference in my testing. It's also a general purpose animation toolkit, which you don't often need
  • motion is only 9.4kB, but doesn't offer React bindings (yet)

Wiggly is only 2kb. Most of that is wobble, which provides the spring logic. Of course, this low weight comes with a few limitations:

  • Wiggly only animates numeric values (eg. 0 to 1), not color or string values (eg. red to blue or #000 to #fff). If you want this, you can animate a value between 0 to 1 and map the change yourself using a library like chroma.js to do the math.
  • Wiggly only gives you values & CSS variables, not styles. You need to manually assign variables to a transform or whatnot. This gives you more control, but it takes a little more work.

Acknowledgements

Wiggly illustration was made by Hannah Lee.