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

@tokens-studio/graph-engine-example-workspace

v3.0.0

Published

Example workspace for the graph engine

Downloads

4

Readme

Graph Engine VS Code example workspace

This is an example workspace showing an idealized layout for the system as well as examples of settings to help a user organize their graph materials easily

Breakdown

│   .tsgraphrc
│   metadata.json
│   package.json
│   tsconfig.json
│   user.json
│
├───assets
│   └───audio
│           example.wav
│
├───capabilities
├───editor
│   ├───controls
│   ├───icons
│   ├───nodes
│   └───previews
├───graphs
│   └───test
│           graph.metadata.json
│           graph.tsGraph
│
├───nodes
└───schemas

Let's step through each of these files to explain their function

  1. .tsgraphrc

This identifies the root of the graph project. It contains information on how to find other code files and assets. It also stores version information about the project. Note that this is independent of the package.json version and is used to identify the versioning of the project layout, not the actual code.

  1. metadata.json

This is a file which stores global level metadata for the project such as editor config, logs , etc.

  1. package.json

This is your standard nodejs package.json file. Install your custom nodes, etc here.

  1. tsconfig.json

This is used to support typescript based projects. You do not need to use typescript and can delete this if you wish.

  1. user.json

User specific project info. This should be gitignored and represents info about you as a user such as theming, etc.

  1. assets

This folder is used to store assets for binary or text files. You can potentially lock down file based interactions in a graph to only view the assets folder

  1. capabilities

Capabilities are graph level libraries that can be used to abstract away complexity and blackbox complicated mechanisms, such as file system interactions which might vary greatly depending on the platform where the graph is being executed.

  1. editor

The editor folder contains code specific to your editing experience within the UI.

  1. editor/controls

Controls are used to interact with the ports on a node. These could potentially be very complicated or specific to a use case, so you can either create a new control or override an existing control here.

  1. nodes

You can create your own custom nodes and store them here. The nodes will be made available to your graphs