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

@ivoyant/component-line

v1.0.11

Published

{ properties: { <configuration> }, data: [ { <query> } ] }

Downloads

14

Readme

Line chart component

General information about componetization

Component props structure

{ properties: { }, data: [ { } ] }

Configuration

When a component added to a dashboard a new instance of the component will be created. Each instance could be configured by using UI which is a configuration schema representation.

Configuration based on react-json-schema (https://github.com/mozilla-services/react-jsonschema-form) and consist of 2 parts:

  • JSON schema. A schema definition of a data structure which will be passed to the component instance. It can contain default data which will be passed to the instance.
  • UI schema. UI representation for end-used, it tells what UI widget to display behind JSON property

Data

Data is a structure, consist of a query to a browser-like DB (ALASQL). A component has opportunity to extend, modify or execute a query. Also, a meta information about fields which query can return is available without doing the actual query.

{
  data: [
    {
      tableMeta: {
        allFields: [],
        labelFields: [], // fields which return String type
        valueFields: [string], // numeric fields
        timeField: string // timestamp field
      },
      queryString: object, // squel (https://hiddentao.com/squel/) query object
      alasql: instance, //connection to Alasql,
      execute: function() // function to run a query
}

Metadata

Each component installed to dashboard has its own name and icon. Please set these properties in package.json as icon, title. As optional you can set a description.

Data transformation

If data provided by data source doesn't meet your component requirements you can transform in with @antv/data-set library. Find out more information here ((https://translate.google.com/translate?sl=zh-CN&tl=en&js=y&prev=_t&hl=ru&ie=UTF-8&u=https%3A%2F%2Fantv.alipay.com%2Fzh-cn%2Fg2%2F3.x%2Fapi%2Fdata-set.html%23_DataSet.transforms&edit-text=)