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

@nil-/jwalk

v1.0.1

Published

a library that traverses json like a tree of customizable nodes

Downloads

5

Readme

@nil-/jwalk

A library that walks through JSON data following schema provided. It is a play of words with "jaywalk" but for JSON.

A "jaywalker" is described as a pedestrian that violates the "rules".

In contrary, "jwalk" expects users to provide the "rules" to follow how to traverse the graph.

The only responsibility of jwalk is to execute the nodes by traversing the graph you setup yourself.

Anything you can do inside the nodes is up to your imagination.

Example

import { jwalker } from "@nil-/jwalk";

const j = jwalker()
    .node("Boolean", "boolean", {
        action: ({ value }) => {
            console.log("[BOOL]", "INIT", value);
            return {
                update: (value) => console.log("[BOOL]", "UPDATE", value),
                destroy: () => console.log("[BOOL]", "DESTROY", "-")
            };
        }
    })
    .node("Number", "number", {
        action: ({ value }) => {
            console.log("[Number]", "INIT", value);
            return {
                update: (value) => console.log("[Number]", "UPDATE", value),
                destroy: () => console.log("[Number]", "DESTROY", "-")
            };
        }
    })
    .node("ROOT", "tuple", {
        content: ["Boolean", "Number"],
        action: ({ value, auto }) => {
            console.log("[ROOT]", "INIT", value);
            const { update, destroy } = auto(
                () => {},
                () => {},
                value
            );
            return {
                update: (value) => {
                    console.log("[ROOT]", "UPDATE", value);
                    update(value);
                },
                destroy: () => {
                    destroy();
                    console.log("[ROOT]", "DESTROY", "-");
                }
            };
        }
    })
    .build(null, [true, 100]);

j.update([false, 200]);

j.destroy();

Result

[GROUP]  INIT    [true, 100]
[BOOL]   INIT    true
[Number] INIT    100
[GROUP]  UPDATE  [false, 200]
[BOOL]   UPDATE  false
[Number] UPDATE  200
[Number] DESTROY
[BOOL]   DESTROY
[GROUP]  DESTROY

Limitations

  • Currently, schema validation is expected to be done by the user before build/update. Some considerations is to add zod json validation before execution of each node.

For more information see link