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

lnkd

v0.0.1

Published

Graph transformation toolkit

Downloads

8

Readme

Just a work in progress with a few example packages to help flush out api design.

Decisions

Scope

Which operations / concepts are essential and belong in the core?

(DOM api parallels?)

Edge schema

From/to? Source/target? Unnamed?

edge = {from: 'one', to: 'two', id: 'e1', directed: true}
edge = {source: 'one', target: 'two', id: 'e1', directed: true}
edge = ['one', 'two', {id: e1, directed: true}]

Wrapped or unwrapped components?

let graph = lnkd({nodes: [{id: 'one'}]});
let one = graph.get('one'); // one is a proxy that ties POJO to graph
let edges = one.edges();

VS

let graph = lnkd({nodes: [{id: 'one'}]});
let one = graph.get('one'); // one is just a POJO {id: 'one'}
let edges = graph.edges(one);

Node / edge manipulation

Do we allow the underlying node and edge data to be manipulated directly? Or do we force everything to happen through a helper?

Is it possible to support direct manipulation and incremental indexing?

Selections

What do we call the result of graph.find(selector)? selection/collection/context?

Can we unify selections and subgraphs? How about single component wrappers?

// can these all share a single api? should they?
graph.find(':after(1999)') // includes nodes and edges
graph.find('[age>100]')    // includes nodes
graph.get('kumu')          // includes single node

Plugin implementation / registration

// Self-registration
import lnkd from 'lnkd';

lnkd.fn.find = (selector) {
  // this <> graph
}

let graph = lnkd(...);
graph.find(selector);

VS

// End user responsible for passing graph to everything. No real graph api.
import lnkd from 'lnkd';

export function find(graph, selector) {

}

let graph = lnkd(...);
let selection = find(graph, selector);

VS

// Plugins defined as pure functions but attached to graph api elsewhere.
export function find(graph, selector) { }

---

import lnkd from 'lnkd';

// registration independent from definition
lnkd.use('find', require('./plugins/find'));

let graph = lnkd(...);
graph.find(selector);

Isolation

  • When is structure shared between graphs?
  • When are properties shared between graphs?
  • What do we use when we want fully isolated copies? (graph.clone() vs graph.copy()?)

Performance

How concerned are we about fast insertion/removal times? Lookups?

Should we have built-in field indexing? Or is edge indexing enough?

Similar APIs / libraries