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

three-shader-graph

v0.2.62

Published

Create GLSL shaders with typescript for Three.js

Readme

three-shader-graph

Create shaders with typescript or javascript for Three.js. The library provides the ability to write code that should be familiar to those with experience with GLSL. The Javascript code will be executed to generate GLSL code but the syntax will make it appear as if you are writing shader code direclty in Typescript/Javascript. The Javascript code builds a directed acyclic graph which is used to generate the GLSL code, hence the graph terminology.

Why?

Writing shaders using GLSL for Three.js is not a great developer experience. First of, it is a new language to learn. Second, and more imprtantly, it involves combining chunks of code as strings in order to provide code reusability. Common non-trivial functionality like calculating ligthing is hard to reuse which leads to poor solutions of trying to inject strings of GLSL in multiple places in the built in shaders to add the needed functionality.

Hology Engine

This library is integrated in Hology Engine, a game engine and editor for creating 3D experiences. Check out https://hology.app to get started.

Features

  • Close to 100% support for GLSL language and standard library
  • Reusable Physical and Lambert lighting implementations.
  • Built in fog effect using the Three.js fog parameters defined on the THREE.Scene

Example

const uniformTime = uniformFloat('time');

const diffuse = rgb(0x00ff00);
const color = standardMaterial({ color: diffuse });
const bounce = translateY(sin(uniformTime.multiply(float(5))));

const material = new NodeShaderMaterial({
  color,
  transform: bounce,
  uniforms: {
    time: { value: 0 },
  },
});

const sphere = new SphereGeometry(5, 30, 15);
const mesh = new Mesh(sphere, material);

Experimental WebGPU bridge

createNodeWebGpuMaterial is an intentionally small bridge for using existing node graphs with webgpu-renderer's WGSLShaderMaterial. It retains node output roots so a material can be derived at runtime. Its supported nodes emit WGSL directly: scalar/vector constants and uniforms, arithmetic, sampler2D sampling, typed vertex-to-fragment varyings, and the existing standardMaterial(...) authoring API.

const tint = uniformVec3('tint', new Vector3(0.16, 0.56, 0.95));
const source = createNodeWebGpuMaterial({
  color: rgba(tint.multiplyScalar(uniformFloat('intensity', 1))),
}).compile();

const material = new WGSLShaderMaterial(source);

For standardMaterial, the WebGPU path supports base color/alpha, roughness, metalness, emissive, ambient occlusion, baked light, world-space normal and world position. It evaluates the renderer's directional, point, and spot-light arrays (including renderer shadows) itself, so it is not lit a second time by the generic graph bridge. This keeps the public material call site shared with WebGL and lets the renderer later replace its fixed arrays with Forward+ data behind the same shader-header functions.

Environment/CubeUV lighting, normal-map tangent-frame construction, rect-area lights, sheen, anisotropy, texture arrays, and other GLSL-only nodes are intentionally not ported by this bridge yet; they fail explicitly rather than silently generating incorrect WGSL. The working standard-material, texture-and-varying example is in webgpu-renderer/demo/examples/shaderGraph.ts.

Install

npm install three-shader-graph

Release

  1. Update the version in package.json
  2. npm install && npm run fix && npm run build

Documentation

See the wiki