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

@pylinka/format

v2.1.0

Published

Pylinka project format: parse, serialize (inline↔blob assets), and migrate documents.

Readme

@pylinka/format

The project file format of Pylinka, a GPU-driven node-based particle system for PixiJS.

Anything you export from the editor is a pylinka project document, and this package is the supported way to read and write one.

parse validates and loads a project JSON. It gives clear errors and never throws on keys it does not recognise, so a document written by a newer editor still opens in an older runtime.

serialize writes a project back out with assets either inlined as base64, giving you one portable file, or kept as blob references.

migrate runs versioned schema migrations, which is what keeps old project files loading after the format moves on.

bundleProject / unbundleProject write and read a .pylinka.zip: project.json with every image replaced by an assets/… path, the images themselves, and a meta.json describing the project and each asset. externalizeAssets does the first half alone, for a minimal JSON when your game ships its textures some other way.

npm i @pylinka/format

The usual flow: export from the editor, ship the JSON with your game, hand it to createParticles() from @pylinka/core.

Docs, the node editor and 69 recorded effects: https://pylinka.schmooky.dev

MIT © pylinka contributors