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

@probed/core

v1.3.1

Published

A single-pass JSX-friendly dynamic tree backend.

Downloads

2

Readme

@probed/core

A single-pass JSX-friendly dynamic tree backend. Aka, React without rerenders.

npm gzip size brotli size

CI Coverage Status Total alerts

Installation

npm i -D @probed/core

Getting started

The Probed core is intentionally fairly bare-bones, and this readme speaks only about the general principles at play. If you just want to dive in directly into writing DOM components using JSX, then head over here (soon!).

Components - Basics

Any function can be used as a component. Simple as that.

Calling probe()on a component with a set of arguments will return a Node. Acessing a node's result will evaluate the component if it hasn't been yet.

N.B. While not strictly required, starting every component with an uppercase is a good practice for JSX compatibility.

import {probe} from "@probe/core"

const Add = (x, y) => {
    return x + y;
}

const node = probe(Add, 1, 2);
console.log(node.result);

Dynamic values

Component callbacks are evaluated only once at creation time. Dynamic behavior is accomplished through the use of Dynamic Values.

Creating such a dynamic value is just a matter of calling dynamic(init), and updating them is done setting its current member

const x = dynamic(12);
x.addListener((v)=>console.log(`x is now ${v}`));
x.current = 13;

Reading from potentially dynamic values is done through valueOf() and transform().

import {dynamic, probe, transform} from "@probe/core"

const Add = (x, y) => {
    const totalNow = x + y;
    console.log(`Values at the time Add was called: ${x}, ${y}, ${totalNow} )`);
    
    const result = transform(x, y, (vx, vy)=>{
        console.log("recomputing Add result");
        vx + vy
    });
    return result;
}

const staticNode = probe(Add, 1, 2);
console.log(staticNode.result);

const dynamicVal = dynamic(1);
const dynamicNode = probe(Add, dynamicVal, 2);
console.log(dynamicNode.result);

dynamicVal = 3;
console.log(dynamicNode.result);

TypeScript users have the luxury of forcing parameters to be static:

import {dynamic, Reader} from "@probe/core"

const add = (x: number, y: Reader<number>) => {
    console.log(`Values at the time add node was called: ${x}, ${ y.valueOf()} )`);
    
    const result = dependant(y, (vy)=>x+vy);
    return result;
}

JSX - intrinsics

You can create a custom probe() function bound against a set of intrinsics using createProber() While not strictly necessarry, we highly recommend that you use TypeScript for defining intrinsics mapping, it will ensure full IDE assistance.

import {createProber} from "@probe/core"

const intrinsics = {
    "add" : (x:number, y:number):number => x+y,
    "mul" : (x:number, y:number):number => x*y,
}

const probe = createProber(intrinsics);

// You can probe by the keys of the map
probe("add", 1, 2);

// You can still probe by function
probe((x)=>x + 4, 4);

N.B. JSX compatibility has a few other steps that are beyond the scope of this specific package. See @probe/html (soon!) for an example of a fully realized JSX binding.