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

@mosaicajs/deck

v0.4.1

Published

A deck.gl layer that draws a Mosaica store, for a host with its own Deck.

Readme

@mosaicajs/deck

MosaicaLayer, a deck.gl layer that draws a Mosaica store, for a page that builds its own Deck. Mosaica serves an interactive map over billions of points from one machine, computed over what each viewer may see. The store comes from @mosaicajs/client.

npm install @mosaicajs/deck @mosaicajs/client @deck.gl/core @deck.gl/layers @deck.gl/aggregation-layers @luma.gl/core
import {Deck, OrthographicView} from '@deck.gl/core';
import {createStore} from '@mosaicajs/client';
import {MosaicaLayer, viewInputOf} from '@mosaicajs/deck';

const store = createStore({viewerUrl: 'http://localhost:8080', token});
let viewState = {target: [256, 256, 0], zoom: 0};

// Tell the store where the camera is looking. viewInputOf is null until the store has its frame.
function tell() {
  const input = viewInputOf(store, viewState, deck.width, deck.height);
  if (input) store.setView(input);
}

const deck = new Deck({
  parent: document.getElementById('map'),
  views: new OrthographicView({flipY: true}),
  viewState,
  controller: true,
  layers: [new MosaicaLayer({id: 'mosaica', store})],
  onViewStateChange: ({viewState: next}) => {
    viewState = next;
    deck.setProps({viewState});
    tell();
  }
});

// The first view goes out once the store has its frame, which arrives with `meta`.
store.subscribe('meta', (meta) => {
  if (meta) tell();
});

For a picture of the world under the points, basemapLayers(store, view, value) returns the deck.gl layers to put before MosaicaLayer: 'world' (the server's world outline, on a view with a map projection), {tiles, attribution} (a tile server of your choosing, on a view with a tileScheme), or {image, bounds}. Its code loads the first time it is called.

deck.gl and luma.gl are peer dependencies.

Documentation: TypeScript client reference. Licence: Apache-2.0.