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 🙏

© 2024 – Pkg Stats / Ryan Hefner

glslify-api

v1.1.0

Published

An API and accompanying client for generating glslify shaders in the browser

Downloads

3

Readme

glslify-api experimental

An API and accompanying client for generating glslify shaders in the browser.

This is done by running glslify in the browser, but redirecting its functions to read and resolve modules to a thin server. Files are cached locally using level.js to speed up the bundling speed after the first run – it can even work offline after downloading the required package once!

See the example directory for a simple example.

NPM

Usage: Server

handle = api([cachedir])

Returns an express-style route handler. cachedir is the location to store temporary packages (using npm-file), and defaults to .glslify.

handle(req, res, next)

Given a request and response pair, handle a route. Will call next if there is an error or a appropriate route is not found.

Usage: Browser

getShader = api(serverURI, [options])

Returns a function for compiling shaders within the browser. serverURI should be the URI where you're hosting your copy of the glslify-api server – if you don't pass one in that's OK too, there's one being hosted at glslify.shader.club.

Available options:

  • ttl: the maximum amount of time to cache a file locally, in milliseconds.

getShader(source, done(err, result))

Pass in a shader body source, and done will be called with either an error or the glslified shader when ready.

HTTP API

GET /

Should return:

{
  "glslify": true
}

POST /-/shader

Pipe a whole shader to the request body and get a glslified shader in return. This is a little more blunt than the approach in the client, but can be useful for small, quick experiments.

GET /:package/:file...

Returns the raw contents of file from the package package on npm.

License

MIT. See LICENSE.md for details.