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

@blockprotocol/graph

v0.3.4

Published

Implementation of the Block Protocol Graph service specification for blocks and embedding applications

Downloads

102,385

Readme

Block Protocol – Graph module

This package implements the Block Protocol Graph module for blocks and embedding applications.

Getting started

If you are a block author, we have several block templates available which use this package

npx create-block-app@latest --help

The best way to get started is to read the docs.

stdlib

The package exports a standard library of helper functions for interacting with a Subgraph, available from "@blockprotocol/graph/stdlib". For example

import { getOutgoingLinkAndTargetEntities } from "@blockprotocol/graph/stdlib";

// find the outgoing links and target entities for a given entity
const linkAndTargetEntities = getOutgoingLinkAndTargetEntities(
  subgraph,
  "entity-123",
);

for (const { linkEntity, rightEntity } of linkAndTargetEntities) {
  // do something with each link and the entity it points to
}

For a full list of available functions see src/stdlib.ts

Initializing a graph module handler

If you want to roll your own block template or embedding application, you can use this package to construct a handler for graph module messages.

  1. yarn add @blockprotocol/graph or npm install @blockprotocol/graph
  2. Follow the instructions to use the graph module as a block or an embedding application

Blocks

To create a GraphBlockHandler, pass the constructor an element in your block, along with any callbacks you wish to register to handle incoming messages.

React

For React, we provide a useGraphBlockModule hook, which accepts a ref to an element, and optionally any callbacks you wish to provide on initialization.

See npx create-block-app@latest my-block --template react for an example.

Custom elements

For custom elements, this package exports a BlockElementBase class which uses the Lit framework, and sets graphModule on the instance for sending graph-related messages to the embedding application.

See npx create-block-app@latest my-block --template custom-element for an example.

Embedding applications

You should construct one GraphEmbedderHandler per block.

It is not currently possible to wrap multiple blocks with a single handler.

To create a GraphEmbedderHandler, pass the constructor:

  1. An element wrapping your block
  2. callbacks to respond to messages from the block
  3. The starting values for the following messages:
  • blockEntitySubgraph: the graph rooted at the block entity
  • readonly: whether or not the block should be in 'readonly' mode

These starting values should also be passed in a graph property object, if the block can be passed or assigned properties.

See the here or check the TypeScript types for message signatures.

import { GraphEmbedderHandler } from "@blockprotocol/graph";

const graphModule = new GraphEmbedderHandler({
  blockEntitySubgraph: { ... }, // subgraph containing vertices, edges, and 'roots' which should be a reference to the block entity
  readonly: false,
  callbacks: {
    updateEntity: ({ data }) => updateEntityInYourDatastore(data),
  },
  element: elementWrappingTheBlock,
});

React

For React embedding applications, we provide a useGraphEmbedderModule hook, which accepts a ref to an element, and optionally any additional constructor arguments you wish to pass.

import { useGraphEmbedderModule } from "@blockprotocol/graph";
import { useRef } from "react";

export const App = () => {
  const wrappingRef = useRef<HTMLDivElement>(null);

  const blockEntitySubgraph = { ... }; // subgraph containing vertices, edges, and 'roots' which should be a reference to the block entity

  const { graphModule } = useGraphEmbedderModule(blockRef, {
    blockEntitySubgraph,
  });

  return (
    <div ref={wrappingRef}>
      <Block graph={{ blockEntitySubgraph }} />
    </div>
  );
};