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

shared-effects

v0.0.2

Published

Shared Files for Fancy Feature Pod

Readme

shared-effects

Shared effects for the text and effects team

Warps file (JSON)

Json file values

| Value | Type | Description | Details | | --- | --- | --- | --- | | warpId | integer | The id for the warp | This id should be unique across all warps (even disabled ones). Also it is saved on the Canvas api to reference and know which warp is to be used | | version | integer | The version of the warp file the warp was initially released in | When creating a new version, increment the current version in this readme, and then add the new version to the new contours | | name | string | The name of the warp | This name should not be used in the clients. Each client will need to map strings from the | | enabled | boolean | Whether or not the warp is enabled | When we modify a warp, we will need to disable the current warp, and add the new warp. This is so previously saved warped objects will look the same even if the contours that were used to warp them have been changed | | sortOrder | integer | The order that warps appear in the list | This number should be sorted ASC | | defaultTValue | number (0-1) | The default value to be used for contours/warps if the tValue is not changed | If the default value is used, this is the basic look and feel of the warp. It is the value that should be used to when initially a warp is selected, before tValue is manipulated | | minYControlContours | [string (svg path)] | The contours that define the warps bottom path | | | maxYControlContours | [string (svg path)] | The contours that define the warps top path | |

Current version: 1

When editing the warps.json

  1. Make you changes
  2. Go to https://www.jsonschemavalidator.net/
  3. Paste warps-schema.json and changes to warps.json
  4. Validate