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

origami-loaders

v0.1.2

Published

Loaders that fold: ten 3D origami models, from a paper crane to a jumping frog, as live SVG. One web component, zero dependencies.

Readme

origami-loaders

Loaders that fold. 3D origami animations rendered as lightweight SVG — no canvas, no WebGL, no dependencies.

See them fold → Every model, look and paper colour, live, in example apps. Pick one and copy its tag.

A framework-agnostic web component: drop <origami-loader> into any page, React, Vue, Svelte or plain HTML.

Install

npm i origami-loaders

With a bundler, import the package once. It registers the <origami-loader> element as a side effect. The OrigamiLoader class is also exported. It is safe to import during server rendering (Next.js, Nuxt, SvelteKit, Astro): the element registers only once the page runs in a browser.

import 'origami-loaders';
<origami-loader look="ink"></origami-loader>

Without a bundler, load the IIFE build from jsDelivr:

<script src="https://cdn.jsdelivr.net/npm/origami-loaders"></script>
<origami-loader look="blueprint" theme="dark"></origami-loader>

Attributes

| Attribute | Values | Default | Description | | ---------- | ---------------------------------------- | ------- | ----------- | | model | crane, plane, pleat, envelope, boat, frog, swan, heart, whale, fox | crane | Which origami model to fold. | | look | ink | blueprint | graphite | paper | ink | Rendering style. | | theme | light | dark | auto | auto | auto follows prefers-color-scheme. | | speed | number | 1 | Playback speed multiplier. | | progress | 0..1 | unset | When present, the loader is in determinate mode and shows that point of the fold sequence instead of playing. | | paused | boolean attribute | unset | Pauses playback. |

CSS custom properties

| Property | Used by | Description | | ------------- | ----------------- | ----------- | | --ol-ink | all looks | Line color. | | --ol-bg | all looks | Face fill used to hide lines behind other faces. Should match the page background. | | --ol-front | paper | Front-side paper color. | | --ol-back | paper | Back-side paper color. | | --ol-stroke | all looks | Line width, e.g. 1.5px. |

Size is set with CSS width / height (default 160px square).

origami-loader {
  width: 96px;
  height: 96px;
  --ol-ink: #1b1b1d;
  --ol-bg: #fff;
  --ol-stroke: 1.5px;
}

JavaScript API

const el = document.querySelector('origami-loader');

el.duration;      // total length of the fold sequence, in seconds
el.seek(2.5);     // jump to a time, in seconds
el.currentStep;   // { index, diagram, label }
el.stepCount;     // steps on the paper diagram: 14 for the crane, 7 for the plane

el.addEventListener('ol-step', (e) => {
  const { index, diagram, label } = e.detail; // fired when the step changes
});

Real progress

Set progress as work advances, then call complete() when it is done. The model plays its ending (the crane flies off, the plane leaves), fires ol-complete, and stays empty until you start again.

upload.on('progress', (p) => el.setAttribute('progress', p)); // 0 to 1
upload.on('done', () => el.complete());
el.addEventListener('ol-complete', () => showSent());
el.restart(); // or set progress again to fold a fresh sheet

Models

| Model | What it does | | --- | --- | | crane | The default. All 14 steps of the classic diagram, about 25 seconds a loop, then it flies off. | | plane | The classic dart in 7 steps. Circles once, then flies off. | | pleat | An accordion that breathes. Made for "thinking" and other waits with no end in sight. | | envelope | Four corners to the centre, so progress maps neatly: a quarter of the work, one corner. | | boat | A sailboat in three folds. Rocks on the water, then sails off. | | frog | The traditional jumping frog, from a waterbomb base. The back legs are a squash fold, and its pleat is a spring: it hops twice, then hops away. | | swan | The traditional swan: a kite, folded in half, then the neck and head are pulled up into place. Drifts on the water, then glides off. | | heart | The classic heart, folded on the side you see. It beats. | | whale | The traditional whale, from a fish base: the rabbit ears become its flippers. Swims, flicks its tail, then dives. | | fox | A fox's face. Tilts its head and twitches its ears. |

Pick one with the model attribute:

<origami-loader model="plane"></origami-loader>

Looks

  • ink — line art, hidden lines removed.
  • blueprint — see-through wireframe with diagram-style fold lines.
  • graphite — monochrome with soft light shading.
  • paper — two-tone origami paper.

Status

The paper crane folds through all 14 steps of the classic diagram, about 25 seconds per loop: pre-creases, square base, petal folds on both sides, narrowing, inside reverse folds for the neck, tail and head, then the wings spread and it flies off while a new sheet drops in.

  • [x] Folding engine: folds against the paper as it lies, solved compound folds, layer stacking, 3D projection, depth sorting
  • [x] The crane, all 14 steps
  • [x] Four looks, light and dark, recolourable, with procedural paper grain
  • [x] Progress mode, reduced motion, pauses off screen
  • [x] A second model, the paper plane
  • [x] Ten models: crane, plane, pleat, envelope, boat, frog, swan, heart, whale, fox
  • [x] A fold check in the test suite that catches the wrong layer showing, folds that undo themselves, and torn creases
  • [ ] Static SVG export for no-JS / <img> use
  • [x] Paper look: models can start coloured side down, as real ones do, so the plane and envelope fold the colour out
  • [x] No crease ever comes apart, in any model: the swan's neck and head are pulled up the way paper moves, and the whale's tail is a plain mountain fold
  • [x] Paper that flexes. The crane's neck, tail and head are inside reverse folds, which paper can only make by spreading its layers. The layers open along a soft line, the point swings through, and they close again
  • [x] The crane shows only its coloured side, wings included, as a crane folded from one-sided paper does

How it works

A model is written the way origami is taught: one fold at a time, against the paper as it currently lies (src/models/crane.ts).

  1. Folds cut the paper. Each fold splits the faces it passes through along the fold line, so the crease pattern builds itself (src/fold.ts).
  2. Joints move the faces. A hinge rotates faces about a fold line; joints chain, so a flap can fold while it is being lifted. A pull (the swan's neck and head) is worked out exactly: the crease at the point's base swings round, the wedge of paper between the old crease and the new one turns over, and the point unfolds about the old crease by whatever keeps its spine between the two sides, so nothing comes apart on the way. An inside reverse fold (the crane's neck, tail and head) mirrors the point across its crease and tucks it between its own two sides. Stiff, flat paper cannot do that with everything else shut, because the point has to pass between two layers that touch, so real paper flexes. Here the flex is one soft line on each side, square to the crease: the paper between that line and the crease lifts by atan(sin a / tan κ) as the point folds by a, where 90° − κ is the angle between the point's spine and the crease. That opens a mouth for the point to swing through and shuts it again at the end, with every crease joined all the way. A soft line leaves no crease mark.
  3. Compound folds are solved. The square base and the petal folds move several creases at once. Those angles are left free, pin says which corners must stay together, and a small Gauss–Newton solver works out the angles along the whole motion so the paper never tears. Some are worked out exactly instead. In the frog's waterbomb base, as each side triangle turns in by θ, the top comes down by γ = 2·atan(tan(θ/2)/√2). In its squash, the bottom rises in front, each side flap's middle triangle turns over just fast enough to keep its two creases 45° apart, and the lower triangle swings out between them. The whale's rabbit ears are tracked numerically so the two halves of each ear meet back to back.
  4. Layers are tracked. After every step the engine works out which face ended up on top wherever two overlap, and gives every face a layer height, so flat stacks have real thickness. Paper that stands up, like a crane's spread wings, keeps its stacking turned with it.
  5. Rendering. Faces are projected with a perspective camera and shaded by how they face a light. Faces lying flat together are drawn as one panel and painted back-to-front with plane tests and a topological sort; where no plane separates two panels, the one nearer the eye where they actually overlap goes on top (src/scene.ts).
  6. Paper. Paper Shaders' paper-texture shader renders the grain once per page on a hidden WebGL canvas; the result is baked into an image that each panel maps in sheet space, so the grain folds with the paper (src/paper-shader.ts, with a small CPU fallback in src/texture.ts).
  7. Looks are CSS (src/styles.ts). The paper look colours the front of the sheet; a model compiled with colourDown starts with the front facing away, the way you fold coloured paper, so the folds bring the colour out.

The crane compiles in about 100 ms on first use. A frame costs about 1 ms of script. The whole package, all ten models included, is about 22 kB gzipped.

Development

npm test also runs a fold check over every model (test/inspect.ts, under a second). At several moments in every step it lays the frame out exactly as the renderer does and fails if a farther layer is painted over a nearer one (the wrong side of the paper showing), if a face rides folds that undo each other, or if any crease comes apart at any of 40 moments in the step. There are no exceptions.

npm install
npm run typecheck
npm test
npm run build      # dist/ bundles + types, and a self-contained demo/dist/index.html
npm run demo       # build, then print the demo page path
npm run capture    # screenshots + video of the demo (needs Playwright and ffmpeg)

Releasing

Publishing runs in GitHub Actions when a v* tag is pushed (.github/workflows/publish.yml). It typechecks, tests, builds, checks the tag against the version in package.json, then publishes with provenance: a signed record on npm of the commit and workflow that built the package. What changed in each version is in CHANGELOG.md.

The first release, with a token

The package does not exist on npm until the first release, so that one release uses a token.

  1. On npmjs.com, go to Access Tokens and generate a granular access token:

    • Bypass two-factor authentication ticked, so the workflow can publish without a code from your phone.
    • Packages and scopes: Read and write (publish and stage) on All Packages. The package cannot be picked by name until it exists.
    • Expiration: 7 days. It is only needed once.
  2. In the GitHub repo, go to Settings, Secrets and variables, Actions, and add the token as a repository secret named NPM_TOKEN.

  3. Tag the release commit on main and push the tag:

    git tag v0.1.0
    git push origin v0.1.0
  4. Follow the Publish run in the repo's Actions tab. When it is green, the package is at npmjs.com/package/origami-loaders.

  5. Delete the NPM_TOKEN secret and revoke the token on npmjs.com. It has done its job.

Every release after, with no token

From then on, npm trusts this repo's publish workflow directly (trusted publishing), so no token is stored anywhere. npm stops letting tokens publish directly in January 2027, so this is the way to release from then on. The workflow needs no change: npm tries trusted publishing first and falls back to a token only when there is one.

  1. On npmjs.com, open the package's Settings, find Trusted Publisher, choose GitHub Actions and enter rishiashar, origami-loaders and publish.yml. The next publish must happen within 2 days of adding it, or the connection expires and has to be added again, so do this when the next release is ready.

  2. Bump the version, tag it and push:

    npm version 0.1.1 --no-git-tag-version   # or edit package.json by hand
    git commit -am "Release v0.1.1"
    git tag v0.1.1
    git push && git push --tags

    Or, once the version bump is on main, either:

    • run the Publish workflow on main (Actions, Publish, Run workflow). It publishes the version in package.json, then creates its tag and GitHub release with the notes from CHANGELOG.md; or
    • publish a GitHub Release with a new tag such as v0.1.1 on main (Releases, Draft a new release). Creating the tag starts the same publish.
  3. Once that release is out, go to the package's Settings, Publishing access, and choose Require two-factor authentication and disallow tokens, so a leaked token can never publish.

Credits

The paper texture comes from the paper-texture shader in Paper Shaders (Apache-2.0), rendered once per page and baked into the grain that folds with the paper. It loads on demand as its own chunk; texture="grain" uses a smaller built-in grain instead, and texture="none" turns texture off. See THIRD_PARTY_NOTICES.txt.

License

MIT