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

gl-buffer-snoop

v1.0.0

Published

Intercepts uploads to WebGL buffers in order to keep track of their expected value on the GPU.

Downloads

8

Readme

gl-buffer-snoop

Intercepts uploads to WebGL buffers in order to keep track of their expected value on the GPU.

Designed solely with the intention of testing packages that interact with WebGL buffers. It's probably not something you should be using in an actual app/demo, so approach with caution.

Usage

NPM

snoop(gl)

Before using your WebGL context at all, you should let gl-buffer-snoop do its thing by passing it the context in question:

var canvas = document.createElement('canvas')
var gl = canvas.getContext('webgl')

require('gl-buffer-snoop')(gl)

This will override a few of the context's methods to keep track of outgoing data, along with providing a new method for you to use to retrieve a buffer's data:

gl.getBufferData(buffer)

Given an instance of a WebGLBuffer, returns our local copy of the data it should have stored on the GPU. This is returned as a Uint8Array, but you can easily convert it to other types too thanks to the magic of typed arrays. For example:

var buffer = gl.createBuffer()
// ...
var rawData = gl.getBufferData(buffer)
var floatData = new Float32Array(rawData.buffer)

If you're using this with gl-buffer, you can just use the handle property to access the underlying buffer instance:

var buffer = require('gl-buffer')(gl, [1, 2, 3])
var rawData = gl.getBufferData(buffer.handle)
var floatData = new Float32Array(rawData.buffer)

console.log(floatData) // [1, 2, 3]

License

MIT. See LICENSE.md for details.