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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@clevercanary/data-explorer-ui

v71.0.0

Published

## General info

Downloads

170

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

hunterckxhunterckxnoopdognoopdog

Keywords

Readme

data-explorer-ui

General info

  • src contains TypeScript source files; lib will contain compiled JavaScript, which is what should be imported by the external application.
  • Import paths used by the external application need to specify the full path starting from the package name, in the form @clevercanary/data-explorer-ui/lib/<path>, where <path> is the path of the file within the lib folder.

Developing the Clever Canary Data Explorer alongside Clever Canary Data Browser

  1. Clone this repository into the same parent folder as the Clever Canary Data Browser.
  2. Set node version to 16.15.0 (this is also the version used by the Data Browser).
  3. In the Data Explorer packages/data-explorer-ui directory (e.g. data-explorer/packages/data-explorer-ui):
    • Run npm ci.
    • Bump the version number in package.json e.g. npm version <update_type>.
    • Run npx tsc (this should be run when this repository is first downloaded and when any changes are made to the source files; one way this can be done more efficiently is by setting the default build task in VS Code so that it can be done with a keyboard shortcut).
  4. In the Data Browser explorer directory (e.g. data-browser/explorer):
    • Run npm ci.
    • Update the @clevercanary/data-explorer-ui dependency in the package.json file to use the new version of data-explorer-ui.
    • Run npm link ../../data-explorer/packages/data-explorer-ui, which will create a symlink in node_modules pointing to data-explorer-ui.
    • If any packages are later installed or uninstalled, the symlink will need to be created again, which can be done with the same command or by running npm link @clevercanary/data-explorer-ui.