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

widget-gauge

v1.5.20

Published

REWidget widget-gauge

Downloads

4

Readme

<widget-gauge>

Installation

npm i widget-gauge

Usage

<script type="module">
  import 'widget-gauge';
</script>

<widget-gauge></widget-gauge>

Expected data format

The following format represents the available data :

{
  "settings": {

  },
  "dataseries": [{
    "label": "Demo Gauge 1",
    "unit": "°C",
    "valueColor": "black",
    "sections": [-20, 80, 90, 120],
    "backgroundColors": [
      "#AAC8A7",
      "#F1C27B",
      "#FF9B9B"
    ],
    "averageLatest": 1,
    "data": [{
      "value": 90,
      "pivot": "Frankfurt"
    },{
      "value": 40,
      "pivot": "Berlin"
    },{
      "value": 70,
      "pivot": "Berlin"
    },{
      "value": 200,
      "pivot": "Frankfurt"
    },{
      "value": 20,
      "pivot": "München"
    }]
  },{
    "label": "Demo Gauge 2",
    "unit": "Pa",
    "valueColor": "green",
    "averageLatest": 1,
    "data": [{
      "value": 79
    }]
  }]
}

Development

To use the widget locally during development clone the widget repo and start the dev server:

npm run start

This runs a local development server that serves the basic demo located in demo/index.html

If you want to use the widget inside another project X, then add the widget as npm module to the project X as usual. i.e. in the folder of X

npm i widget-gauge

To avoid releasing the widget-gauge on every change and updating the node_modules in X you can "link" the package locally.

Go to your local widget-gauge git repo and do

npm link

This create a global symbolic link on your environment. Now go to your project X git folder and do

npm link widget-gauge

This replaces the already imported widget-gauge package with your local widget-gauge git repo. Since this node module is linked all changes you make in your local widget-gauge repo will immediately be visible in project X.