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

@mozaik/ext-json

v0.4.0

Published

A Mozaïk extension providing generic widgets to be used to display remotely fetched json data

Downloads

15

Readme

Mozaïk remote json widgets

This extension contains generic widgets to be used to display remotely fetched json data.

Widgets

JsonKeys

Display a list of json keys/values.

parameters

key | required | description ----------|----------|----------------------------------------------------------------------- title | no | Override widget title, default to url value url | yes | The URL to use to fetch the json headers | no | An optional object containing http headers to send with the request

CustomJson

Use a template to display json data.

parameters

key | required | description -----------|----------|----------------------------------------------------------------------- title | no | Override widget title, default to url value url | yes | The URL to use to fetch the json headers | no | An optional object containing http headers to send with the request template | yes | The template to be used to display json data

JsonStatus

Display a status depending on json data.

parameters

key | required | description ---------------------|----------|----------------------------------------------------------------------- title | no | Override widget title, default to url value url | yes | The URL to use to fetch the json headers | no | An optional object containing http headers to send with the request template | yes | The template to be used to display json data statuses | yes | An array of rules used to define current status statuses[n].assert | yes | The assertion to be made on fetched json data, see format statuses[n].status | yes | Resulting status if assertion is met, must be one of: unknown, success, warning, error statuses[n].label | no | An optional label to put under the status icon if assertion is met

assertion format

Assertions support several types:

equals

checks that the resulting value strictly equals expectation

statuses:
  - assert: equals(my_key, status_ok)
    status: success

will check that my_key equals status_ok.

contains

checks that the resulting value contains expectation

usage:

statuses:
  - assert: contains(my_key, ok)
    status: success

will check that my_key is contains ok.

matches

checks that the resulting value matches regexp

usage:

statuses:
  - assert: matches(my_key, (ok|success)$)
    status: success

will check that my_key is a matches regexp /(ok|success)$/.

truthy

checks that the value results in a truthy value

usage:

statuses:
  - assert: truthy(my_key)
    status: success

will check that my_key is a truthy value.

falsy

checks that the value results in a falsy value

usage:

statuses:
  - assert: falsy(my_key)
    status: error

will check that my_key is a falsy value.