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

texturestore

v0.1.0

Published

A self memory-managed place to store Three textures

Downloads

3

Readme

TODO

  • A configuration manager, to deal with different datasets, their LOD, chunk size, URL pattern, etc.
  • Wrapper object for [texturestore + bufferqueue] that will expose very few of their logic. Internally, the chunk id will be its URL, but this should not be exposed
  1. The dataset/plane intersection establishes a list of chunks that could be needed
  2. We establish a priority upon which we desire to get the chunks, based on the LOD we need
  3. We query the texturestore with this priority, some chunks may already be in store, some may have to be downloaded using the priority queue

How the chunk query works

  1. send a getChunk request to the wrapper (using dataset ID, LOD, voxel offset x, y, z)
  2. Provide a callback to this request, to be called with the chunk as argument
  3. looking in store if available

Case A: The chunk is available

  1. straight call the callback with the chunk object

Case B: The chunk is not available

  1. Ask bufferqueue to put it in queue with the priority the chunk was given earlier
  2. download progresses...
  3. download ends, the bufferqueue 'success' event is called with the buffer and the URL
  4. the wrapper looks up