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-editor

v4.3.0

Published

UI for the graph engine

Downloads

579

Readme

@tokens-studio/graph-editor

Version License

Description

Graph editor component

Installation

To use the @tokens-studio/graph-editor package in your project, you can install it via npm:

npm install @tokens-studio/graph-editor

Basic Usage

To use the exported editor component, make sure to import the global styles as well:

import React from 'react';
import { Editor } from '@tokens-studio/graph-editor';
//Load the required styles
import '@tokens-studio/graph-editor/dist/index.css';

function App() {
  return (
    <div>
      <Editor />
    </div>
  );
}

export default App;

API

The Editor component allows you to build and manage token resolver graphs in your application. Below is an example of how to use the Editor component along with its API.

import React, { useRef } from 'react';
import { Editor } from '@tokens-studio/graph-editor';
import '@tokens-studio/graph-editor/index.css'; // Make sure to import the global styles

function MyGraphEditor() {
  const editorRef = useRef(null);

  // Function to handle saving the graph
  const handleSave = () => {
    const editorState = editorRef.current.save();
    // Use the editorState containing nodes, edges, and node states as needed
    console.log(editorState);
  };

  // Function to handle loading the graph
  const handleLoad = () => {
    const data = /* Fetch your graph data */;
    editorRef.current.load(data);
  };

  return (
    <div>
      <Editor ref={editorRef} />

      {/* Buttons to trigger the save and load functions */}
      <button onClick={handleSave}>Save Graph</button>
      <button onClick={handleLoad}>Load Graph</button>
    </div>
  );
}

In the example above, we use the useRef hook to create a reference to the Editor component. This allows us to interact with the editor imperatively using the save() and load() functions.

save(): The save() function is called on the Editor component's ref, and it returns the current state of the editor. The state includes information about nodes, edges, and node states.

load(): The load(data) function allows you to load a specific graph data into the editor. You can fetch the data from an external source or use data from a previously saved state.

Development

We need to force the cypress react selector to use a version of resq that supports 18.2.0. This is done through resolutions and by manually adding it as a dev dependency