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

arbor-dashboard

v1.53.0

Published

A tool to create responsive dashboards with charts

Readme

data.responsive_charting_dashboards

An npm package of responsive charting components for data visualisation

Getting Started

Prerequisites

  • Node.js
  • Yarn package manager

Installation

  1. Clone the repository and install dependencies:
yarn
  1. Install backend dependencies:
cd local/backend
yarn
  1. Install frontend dependencies:
cd local/Frontend
yarn

Running the Backend

  1. Navigate to the backend directory:
cd local/backend
  1. Start the backend server:
node app.js
  1. Verify the backend is running by visiting: http://localhost:3000/

Running the Frontend

  1. Navigate to the frontend directory:
cd local/Frontend
  1. Start the Frontend
npm run dev
  1. The frontend will be available at: http://localhost:5173/

Developing with SIS

Note: this is only recommended for end to end developing - for general developing of charts in this library use the packaged dev server, usage guide here

To watch for changes in your local version of this project as a dependency in SIS (or another project) instead of the published npm version, do the following. Note it is extremely flaky and to be perfectly honest I've found if any of these steps goes wrong or happens in the wrong order you're best just to restart your laptop (or ideally buy a new one) and start it all again.

Prerequisites

You'll have to have fe-library running in develop mode (or whichever project is consuming this watching for changes. If you're using this in a different project, adapt the commands for fe-library to whichever package manager & transpiler you are using).

1. Clean up node modules (keeping lock files)

In both this project root and fe-library/client, run:

rm -rf node_modules

2. Install dependencies

In each repo, run:

yarn install

4. Symlink the arbor-dashboard package

In this project root, run:

yarn link

In fe-library/client, run:

yarn link arbor-dashboard

5. Symlink react from fe-library

This is to resolve conflicts in different versions. In fe-library/client, run:

cd node_modules/react && yarn link && cd ../react-dom && yarn link && cd ..

Then in arbor-dashboard, run:

yarn link react && yarn link react-dom

6. Build fe-library in watch mode

In fe-library/client run:

yarn run grunt

7. Build arbor-dashboard (this package) in watch mode

In this project root, run:

yarn webpack --watch

8. Reinstall or re-link after any yarn install

If you run yarn install in either repo, you may need to repeat the yarn link steps to restore symlinks.

9. Troubleshooting

  • If you see missing files (e.g., RefreshUtils.js), delete node_modules and reinstall.
  • If you see the React hooks/dispatcher error, check for duplicate Reacts.
  • Only one version should appear, and only in the client’s node_modules.