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

@buggyorg/dynatype-network-graph

v0.1.12

Published

# Usage

Downloads

34

Readme

Dynatype Network Graph

Usage

| function | description | |----------|-------------| | addTypeConversion (processGraph, convertGraph) | Adds translator nodes for type conversion to the processGraph using only translations which are defined in the convertGraph |

Input Process Graph

The process graph is a directed multigraph.

Each node which doesn't represent a port should have the label: processNode. Nodes which represent ports should have the datatype of the output/input signal as label. The id of port-nodes should be the id of the corresponding processNode + ('_OUT_' | '_IN_') + <a number> to differentiate between different input/output ports.

Edges from port to port should have the label edge and edges between process nodes and ports should have the label processNode_in resp. processEdge_out.

Convert Graph

The convert graph is a directed graph.

The nodes should have it's datatype as label and id.

An edge from a first node to a second node should have the label: id_of_the_first_node + ':' + id_of_the_second_node.

Returned Process Graph

The returned process graph is an expansion of the input process graph.

The edges between two ports with different datatypes are removed. Instead translator nodes with input and output port-nodes are inserted. The translator nodes have the id : id_of_port-node_with_first_datatype + ':' + id_of_port-node_with_second_datatype + <a number> (to identify the different type conversions). The label is first_type + ':' + second_type. The input and output port-nodes of the translator have the id of the corresponding translator_node + ('_OUT_' | '_IN_') + <a number>, and the label translator_in resp. translator_out.