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

@layera-labs/orbit-effects

v1.0.0-beta.4

Published

Orbit WebGL Effects and Shaders

Downloads

30

Readme

@layera-labs/orbit-effects

WebGL image effects for the v1 Orbit editor: a brightness / contrast / saturation / temperature adjustment renderer, a multi-light normal-mapped lighting shader, and the GLSL source for both.

npm i @layera-labs/orbit-effects@beta

Beta. 1.0.0-beta.3 under the beta tag; the API moves without notice.

v1 line, which is legacy. It exists because @layera-labs/orbit-core uses it.

These are not the video engine's filters

Worth being clear about, because the names overlap and the difference matters.

The colour grading in @layera-labs/orbit-video is modelled on ffmpeg's eq filter as it actually runs — on the YUV planes, in BT.601 limited range — so that a browser preview and a server-side MP4 export agree to within a few units out of 255. That agreement is enforced by tests that parse the real filtergraph.

Nothing in this package participates in that. These shaders are a straightforward RGB treatment: brightness adds, contrast pivots around 0.5, saturation mixes toward a Rec.601 luma, temperature pushes red up and blue down. They are for adjusting a still image on a canvas. They are not dual-rendered, they have no ffmpeg counterpart, and applying them to a frame will not reproduce what an export produces.

Adjustments

import { AdjustmentRenderer, DEFAULT_ADJUSTMENTS } from '@layera-labs/orbit-effects';

const renderer = new AdjustmentRenderer(image.width, image.height);
renderer.loadImage(image);                       // HTMLImageElement | HTMLCanvasElement | ImageBitmap

const pixels = renderer.render({ ...DEFAULT_ADJUSTMENTS, contrast: 1.2, temperature: 0.05 });
const dataUrl = renderer.renderToDataURL({ ...DEFAULT_ADJUSTMENTS, saturation: 0 }, 'image/png');

renderer.destroy();

render returns ImageData. setSize reshapes the offscreen canvas; destroy releases the GL context, textures and buffers, and you should call it — a WebGL context is a scarce resource and browsers cap how many a page may hold.

Lighting

LightingShader composites up to four coloured point lights against a normal map. lightingVertexShader and lightingFragmentShader are exported as strings if you want to compile them into your own pipeline rather than use the class.

Browser only

Both classes construct a canvas and ask it for a webgl context in their constructors. There is no software fallback and no Node path. Feature-detect before constructing, and hide the control rather than offering an effect you cannot apply — that is what the editor does.

Links

MIT.