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

datavis-glide

v4.0.0-PRE.0

Published

DataVis GLIDE (Graphical Layer for Interactive Data Exploration)

Readme

DataVis GLIDE Logo

DataVis GLIDE

DataVis is a system for exploring, manipulating, and visualizing data. It consists of multiple components in multiple layers, each responsible for different elements of a complete system. This layer, DataVis GLIDE, provides user interfaces for exploring data. This includes:

  • Complete interactive controls to filter, group, pivot, aggregate, sort, and export data.
  • “Grids” to display tabular data, including a “tree mode” details view for grouped data.
  • “Graphs” to display aggregate results.
  • View saving, column resizing, row selection, floating headers, pagination, and much more.

GLIDE = Graphical Layer for Interactive Data Exploration

How to Use

Vite

Stick this in your package.json obviously.

"dependencies": {
  "wcdatavis": "git+ssh://[email protected]:mieweb/wcdatavis.git",
  "vite": "=7.3.1"
}

Building a Page

Inside a module script tag, import the CSS for DataVis and its dependents. This is necessary when using Vite in this configuration, but not if using a version of DataVis built via Rollup (which uses the PostCSS plugin to automatically extract and bundle all CSS files imported from JS).

import 'jquery-ui/dist/themes/base/jquery-ui.min.css';
import 'sumoselect/sumoselect.min.css';
import 'wcdatavis/wcdatavis.css';

Then just use DataVis like normal:

import { Source, ComputedView, Grid } from 'wcdatavis/index.js';

document.addEventListener('DOMContentLoaded', () => {
  const source = new Source({
    type: 'http',
    url: 'fruit.csv'
  });
  const computedView = new ComputedView(source);
  new Grid({
    id: 'grid',
    computedView: computedView
  }, {
    title: 'DataVis NPM Example (Using Vite)'
  });
});

Make sure you also have a div to contain the grid on the page.

<div id=”grid”></div>

Available Exports

| Export | Description | | -------------- | ------------------------------------------------------------ | | Source | Fetches and decodes data from HTTP, files, or local JavaScript | | ComputedView | Implements filtering, grouping, pivoting, and aggregation | | Grid | Renders data in a table with interactive controls | | Graph | Renders data as charts using Chart.js | | Prefs | User preferences management | | Perspective | Save and restore view configurations | | ParamInput | Parameter input handling for sources |

Traditional Website

  1. Run make setup to get dependencies.
  2. Run make datavis to build the JS file.
  3. Copy dist/wcdatavis.js and dist/wcdatavis.css to your server.
  4. Include them like any other JS and CSS files.

How to Develop

See the Development section of the Manual for a full explanation. What follows is a synopsis.

Quickstart

We use GNU Make to provide a simple interface to the various tools to build and test DataVis.

  • make setup — Installs all dependencies.
  • make datavis — Build the compressed DataVis JS and CSS files.
  • make tests — Same as make, then copy to tests directory, and build test data.
  • make [PORT=] serve — Start local server for interactive testing.
  • make test — Same as make tests, then run automated tests using Mocha & Selenium.
  • make doc — Build all documentation.
    • make jsdoc — Build JS API documentation from comments in the source.
    • make manual — Build the Manual from Markdown files.
  • make clean — Remove all build products and generated test data.
  • make teardown — Resets the development environment.

Tree Structure

  • bin — Contains programs used to build other stuff, e.g. a JSON generator.
  • dist — After compiling with make, contains the JS and CSS files for DataVis.
  • doc — The user & developer manual.
    • md — Manual Markdown source files.
    • html — Manual HTML output files.
  • src — Contains all the source JS files.
    • renderers — Classes for DataVis output.
    • ui — Classes for user interface components.
      • filters — Filter widget implementation.
      • windows — Modal dialogs.
    • util — Classes and modules for utilities.
    • reg — Registry files.
    • lang — Compiled language packs.
  • tests
    • data — Data files for testing and examples.
      • *.json5 — Input for generating JSON files.
      • *.in.json — Input for generating JSON files.
    • lib — Auxiliary JS files to help make writing test cases easier.
    • pages — HTML pages used for running Selenium tests.
      • grid — Tests specifically for the grid.
      • graph — Tests specifically for the graph.
      • qunit — Unit tests, mostly for the view.
    • selenium — Selenium test case files.

History

The original DataVis project consisted of both the data processing and interactive UI functions. It has now been split into two projects: DataVis ACE (this project) and DataVis GLIDE (an intuitive but complete user interface to explore the data).