Détail du package

ts-graphviz

ts-graphviz3.9mMIT3.0.0

Graphviz library for TypeScript

graphviz, dot

readme

Main CodeQL License: MIT All Contributors OpenSSF Best Practices OpenSSF Scorecard Tidelift npm version node version deno version npm # ts-graphviz Graphviz library for TypeScript. 🔗 GitHub npm Reference Ask DeepWiki Sponsor OpenCollective format: Biome test: Vitest build: Vite

What is ts-graphviz? 🎯

ts-graphviz is a comprehensive TypeScript library that provides tools for creating, manipulating, and rendering Graphviz graph descriptions. It offers a type-safe, object-oriented approach to working with the DOT language, which is used by Graphviz for defining graph visualizations.

Key Features ✨

ts-graphviz offers several distinctive features that make it valuable for TypeScript/JavaScript developers working with graph visualizations:

  • TypeScript-friendly API
    • Provides fully typed models for the DOT language with type definitions for graph attributes.
  • Flexible Programming Paradigms
    • Supports both object-oriented and declarative approaches.
  • Multi-level API
    • Offers high-level model APIs and low-level AST manipulation.
  • Modular Design
    • Structured as separate packages for specific functionalities.
  • Cross-platform Support
    • Works in Node.js and Deno environments
  • Extensible
    • Allows extending the type system for custom graph visualization solutions.

Why ts-graphviz? 🤔

ts-graphviz is designed to make it easier for TypeScript and JavaScript developers to work with Graphviz by providing a type-safe, object-oriented API that abstracts away the complexities of the DOT language. It allows developers to create and manipulate graphs programmatically, making it suitable for both small-scale projects and large applications. It is particularly useful for applications that require dynamic graph generation, such as data visualization tools, network analysis, and more.

Getting Started 🚀

Installation 💽

Node.js

This package can then be installed using a package manager.

# npm
$ npm install -S ts-graphviz
# or yarn
$ yarn add ts-graphviz
# or pnpm
$ pnpm add ts-graphviz

Note Want to try before installing? Check out Runkit to see how it works.

Deno 🦕

Deno v1.28 and above supports npm.

You can install and use the package by specifying the following:

import { toDot } from 'npm:ts-graphviz';

Basic Usage 📖

ts-graphviz provides two main approaches to create graph visualizations:

Object-Oriented API

Create graphs using object-oriented programming with classes:

import { attribute as _, Digraph, Subgraph, Node, Edge, toDot } from 'ts-graphviz';

// Create a directed graph
const graph = new Digraph();

// Create nodes
const node1 = new Node('node1', { color: 'red' });
const node2 = new Node('node2', { color: 'blue' });

// Create an edge between the nodes
const edge = new Edge([node1, node2], { label: 'Edge Label' });

// Add elements to the graph
graph.addNode(node1);
graph.addNode(node2);
graph.addEdge(edge);

// Convert to DOT language
const dot = toDot(graph);

// Convert to DOT language
const dot = toDot(G);
// digraph {
//   "node1" [
//     color = "red",
//   ];
//   "node2" [
//     color = "blue",
//   ];
//   "node1" -> "node2" [
//     label = "Edge Label",
//   ];
// }

Declarative API (Factory Function)

Create graphs using a declarative approach with a factory function:


```ts
import { attribute as _, digraph, toDot } from 'ts-graphviz';

// Create a directed graph using the factory function
const graph = digraph('G', (g) => {
  // Create nodes within the graph context
  const a = g.node('a');
  const b = g.node('b');

  // Create an edge between nodes
  g.edge([a, b], { label: 'connects to' });

  // Create a subgraph with its own nodes and edges
  g.subgraph('A', (sg) => {
    const c = sg.node('c');
    const d = sg.node('d');
    sg.edge([c, d]);
  });
});

// Convert to DOT language
const dot = toDot(graph);
// digraph G {
//   "a";
//   "b";
//   "a" -> "b" [
//     label = "connects to",
//   ];
//   subgraph "A" {
//     "c";
//     "d";
//     "c" -> "d";
//   }
// }

Declarative API (React Component)

The @ts-graphviz/react package provides React components for creating Graphviz graphs declaratively with JSX:

import { Digraph, Node, Edge, renderToDot } from '@ts-graphviz/react';

// Define reusable components
const UserCard = ({ id, name, role }) => (
  <Node
    id={id}
    shape="record"
    label={
      <dot:table border="0" cellborder="1" cellspacing="0">
        <dot:tr>
          <dot:td bgcolor="lightblue">
            <dot:b>{name}</dot:b>
          </dot:td>
        </dot:tr>
        <dot:tr>
          <dot:td>{role}</dot:td>
        </dot:tr>
      </dot:table>
    }
  />
);

const StatusBadge = ({ status }) => (
  <dot:font color={status === 'active' ? 'green' : 'red'}>
    <dot:b>{status.toUpperCase()}</dot:b>
  </dot:font>
);

// Compose the graph
const TeamStructure = () => (
  <Digraph rankdir="TB">
    <UserCard id="alice" name="Alice Smith" role="Team Lead" />
    <UserCard id="bob" name="Bob Johnson" role="Developer" />
    <UserCard id="carol" name="Carol Davis" role="Designer" />

    <Node
      id="project"
      label={
        <>
          <dot:b>Project Alpha</dot:b><dot:br/>
          Status: <StatusBadge status="active" />
        </>
      }
      shape="box"
      style="rounded,filled"
      fillcolor="lightyellow"
    />

    <Edge targets={["alice", "bob"]} label="manages" />
    <Edge targets={["alice", "carol"]} label="manages" />
    <Edge targets={["project", "alice"]} label="assigned to" style="dashed" />
  </Digraph>
);

// Render to DOT
const dot = await renderToDot(<TeamStructure />);

[!TIP] See the @ts-graphviz/react documentation for comprehensive examples and API reference.

Useful Links 🔗

Documentation 📖

More detailed documentation and examples can be found in the following resources:

  • API Reference
    • See the API Reference for detailed documentation on how to use the library.
  • DeepWiki
    • See the AI generated documentation for more information.
    • And ask questions about the library.
  • Website
    • The official website for ts-graphviz.

Architecture 🏛

See ARCHITECTURE.md for more details.

Security 🛡️

See SECURITY.md for more details.

Package Structure 📦

The ts-graphviz repository is structured as a monorepo containing several packages, each with a specific responsibility:

Package Purpose
ts-graphviz Main entry point providing a high-level API for most users
@ts-graphviz/core Core object models for graph manipulation
@ts-graphviz/ast Parser and AST (Abstract Syntax Tree) handling for DOT language
@ts-graphviz/adapter Platform-specific implementations for rendering graphs
@ts-graphviz/common Shared types and utilities used across packages
@ts-graphviz/react React components for creating and rendering Graphviz graphs

[!TIP] Dependency graph Packages' Dependency graph

Data Flow and Processing Pipeline 🔄

The following diagram illustrates how data flows through the ts-graphviz system, from graph creation to final rendering:

Data flow

  1. Creation Phase: Users create graph models through object-oriented API, React components, or parsing DOT strings
  2. Processing Phase: Models are converted to AST and then to DOT language strings
  3. Rendering Phase: Platform-specific adapters convert DOT strings to visual output formats
    1. The adapters handle platform-specific operations, such as executing the Graphviz dot command in Node.js/Deno, while maintaining a consistent API across environments.

[!TIP] Rendering in the browser is not directly supported by this library, but you can use other libraries like @hpcc-js/wasm-graphviz to achieve rendering in the browser.

Key Data Transformations:

  • Model -> AST: Converts object model to abstract syntax tree
  • AST -> DOT: Generates DOT language string from AST
  • DOT -> AST: Parses DOT language into AST
  • AST -> Model: Converts AST back to object model
  • DOT -> Output: Uses adapters to render visual outputs

The toDot() function from the ts-graphviz package is a composite of fromModel() and stringify(), while the fromDot() function is a composite of parse() and toModel().

Who's using ts-graphviz 📜

[!NOTE] Let us know that you're using ts-graphviz on GitHub Discussions 🙏

Related Projects 💫

Related projects can be found at ts-graphviz GitHub Organization.

The TypeScript/JavaScript ecosystem provides a variety of OSS with the goal of making Graphviz more connected and easier to use.

Contributors 👥

Thanks goes to these wonderful people (emoji key):

Yuki Yamazaki
Yuki Yamazaki

💻 ⚠️ 📖 🤔
LaySent
LaySent

🐛 ⚠️
elasticdotventures
elasticdotventures

📖
Christian Murphy
Christian Murphy

💻 🤔 📖
Artem
Artem

🐛
fredericohpandolfo
fredericohpandolfo

🐛
diegoquinteiro
diegoquinteiro

🐛
robross0606
robross0606

🤔
Blake Regalia
Blake Regalia

🐛
bigbug
bigbug

💬
mrwk
mrwk

💬
svdvonde
svdvonde

💬
Adam
Adam

💬
Trevor Scheer
Trevor Scheer

️️️️♿️
Prem Pillai
Prem Pillai

🐛
nagasawaryoya
nagasawaryoya

💻 ⚠️
YukiSasaki
YukiSasaki

💻 ⚠️
Madd0g
Madd0g

🐛
j4k0xb
j4k0xb

🐛
HKrogstie
HKrogstie

🐛
Nils K
Nils K

🐛
hao2013
hao2013

🚧 👀
Walter Rafelsberger
Walter Rafelsberger

💬
grsjst
grsjst

🐛
Steve
Steve

🐛

This project follows the all-contributors specification. Contributions of any kind welcome!

How to Contribute 💪

The easiest way to contribute is to use the library and star repository.

Questions 💭

Feel free to ask questions on GitHub Discussions.

Report bugs / request additional features 💡

Please register at GitHub Issues.

Development / Bug Fixes 🧑‍💻

See CONTRIBUTING.md.

Financial Support 💸

Support this project by becoming a sponsor. Your logo will show up here with a link to your website. Become a sponsor

OpenCollective Sponsors

Thank you to all our backers! 🙏 Become a backer

OpenCollective Backers

Please support ts-graphviz on Open Collective or GitHub Sponsors.

Note Even just a dollar is enough motivation to develop 😊

ts-graphviz for Enterprise 🏢

Available as part of the Tidelift Subscription.

The maintainers of ts-graphviz and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open-source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use.

Learn more.

License ⚖️

This software is released under the MIT License, see LICENSE.

changelog

ts-graphviz

3.0.0

Major Changes

  • #1363 9328563 Thanks @kamiazya! - 🚨 Breaking Changes: Drop Node.js 18 support

    Minimum required version is now Node.js 20+

    ESM-Only Distribution

    • Remove CommonJS builds: All packages now distribute only ESM (ECMAScript Modules)
    • Package exports: Removed require fields from package.json exports
    • Module type: All packages are now "type": "module"

    🔄 Migration Guide

    For ESM Projects (Recommended)

    {
      "type": "module"
    }
    
    // Import syntax remains unchanged
    import { Digraph, Node, Edge, toDot } from "ts-graphviz";
    import { toFile } from "ts-graphviz/adapter";
    import { parse } from "ts-graphviz/ast";
    

    For CommonJS Projects

    If you are using CommonJS (CJS) and need to migrate to ESM, you will need to update your project to support dynamic imports. This is necessary because the packages no longer provide CommonJS builds.

    Before (CJS)

    // JavaScript (CommonJS)
    function createGraph() {
      // Dynamic import is required because the packages no longer provide CommonJS builds.
      const { Digraph, Node, Edge, toDot } = require("ts-graphviz");
      const graph = new Digraph();
      return toDot(graph);
    }
    

    After (ESM)

    async function createGraph() {
      const { Digraph, Node, Edge, toDot } = await import("ts-graphviz");
    
      const graph = new Digraph();
      // Create your graph...
      return toDot(graph);
    }
    
    // TypeScript (CommonJS)
    // Update tsconfig.json
    {
      "compilerOptions": {
        "module": "Node16",
        "moduleResolution": "Node16"
      }
    }
    
    // Use dynamic imports
    async function createGraph() {
      const tsGraphviz = await import('ts-graphviz');
      const { Digraph, Node, Edge, toDot } = tsGraphviz;
    
      const graph = new Digraph();
      // Create your graph...
      return toDot(graph);
    }
    

    🎯 Benefits

    • Modern JavaScript: Leveraging native ES modules for better performance
    • Smaller bundle sizes: ESM enables better tree-shaking
    • Future-proof: Aligning with the JavaScript ecosystem direction
    • Better TypeScript support: Enhanced module resolution

Minor Changes

  • #1363 9328563 Thanks @kamiazya! - Define Supported environment and Support levels

    To provide clarity on the environments in which ts-graphviz operates, we have categorized support levels:

    Support Levels

    Tier 1: Full Support

    • Definition: Environments that are fully supported, with comprehensive automated testing and maintenance.
    • Environments:
      • Node.js LTS versions: All active Long-Term Support (LTS) versions.
        • If a Node.js LTS version is released, we will ensure compatibility with it.
        • If a Node.js LTS version is deprecated, we will drop support for it in the next major release.
    • Details:
      • We run automated tests on all LTS versions of Node.js.
      • Full compatibility and performance are ensured.
      • Critical issues are prioritized for fixes.

    Tier 2: Active Support

    • Definition: Environments that receive active support with limited automated testing.
    • Environments:
      • Deno Latest LTS version: The latest Long-Term Support (LTS) version of Deno.
        • If a new Deno LTS version is released, we will ensure compatibility with it.
        • If a Deno LTS version is deprecated, we will drop support for it in the next minor release.
      • Node.js Current Release: The latest Node.js release outside the LTS schedule.
        • If a new Node.js current release is available, we will ensure compatibility with it.
        • If a Node.js current release is deprecated, we will drop support for it in the next minor release.
    • Details:
      • Compatibility is maintained, and issues are addressed.

    Tier 3: Community Support

    • Definition: Environments that are not officially tested but are supported on a best-effort basis.
    • Environments:
      • Modern Browsers: Latest versions of major browsers, including:
        • Google Chrome
        • Mozilla Firefox
        • Microsoft Edge
        • Apple Safari
      • Deno Current Release: The latest Deno release outside the LTS schedule.
    • Details:
      • Installation methods are provided.
      • No automated testing is performed.
      • Issues reported by users will be addressed.
      • Targeting the latest versions ensures compatibility with modern web standards.
      • We will not actively test or maintain compatibility with older versions of browsers.

Patch Changes

  • #1363 9328563 Thanks @kamiazya! - Update Develop Environment

    • Drop turbo
    • Upgrade biome to 2.0
    • Upgrade TypeScript to 5.8
    • Upgrade Vite to 7.0
    • Upgrade Vitest to 3.2
    • Upgrade Peggy to 5.0 and drop ts-pegjs
    • Implement new E2E test workflow
  • #1363 9328563 Thanks @kamiazya! - New GitHub Action main workflow and tests

  • Updated dependencies [9328563, 9328563, 9328563, 9328563, 9328563, 9328563, 9328563]:

    • @ts-graphviz/adapter@3.0.0
    • @ts-graphviz/common@3.0.0
    • @ts-graphviz/core@3.0.0
    • @ts-graphviz/ast@3.0.0

2.1.6

Patch Changes

  • Updated dependencies [c043ba9]:
    • @ts-graphviz/ast@2.0.7
    • @ts-graphviz/core@2.0.7

2.1.5

Patch Changes

  • Updated dependencies [d7ff421, d7ff421]:
    • @ts-graphviz/ast@2.0.6
    • @ts-graphviz/common@2.1.5
    • @ts-graphviz/core@2.0.6
    • @ts-graphviz/adapter@2.0.6

2.1.4

Patch Changes

2.1.3

Patch Changes

2.1.2

Patch Changes

2.1.1

Patch Changes

  • #1003 24f4174 Thanks @dependabot! - build(deps-dev): bump vite from 5.1.3 to 5.2.8

  • #1004 fabb8c8 Thanks @kamiazya! - Fix documentation build failed

  • Updated dependencies [24f4174, fabb8c8]:

    • @ts-graphviz/core@2.0.2
    • @ts-graphviz/common@2.1.1
    • @ts-graphviz/ast@2.0.2
    • @ts-graphviz/adapter@2.0.2

2.1.0

Minor Changes

Patch Changes

2.0.0

Major Changes

  • #956 1e4f57a Thanks @kamiazya! - # ts-graphviz v2

    Why?

    Dropping support for Node.js 14 & 16

    We are introducing a major version upgrade to ts-graphviz to ensure better performance, security, and compatibility with the latest improvements in the JavaScript ecosystem. With this upgrade, we will no longer support Node.js 14 & 16, which has reached its End-of-Life (EOL), and set the new minimum guaranteed version to Node.js 18.

    This major version upgrade is necessary due to the following reasons:

    1. Breaking Change: Dropping support for Node.js 14 & 16 is considered a breaking change, which requires a major version upgrade according to semantic versioning principles.

    2. Improved Stability and Performance: By focusing on LTS versions, we can provide a library that benefits from the stability, long-term support, and performance improvements provided by newer Node.js versions.

    3. Security: Ensuring that our library is compatible with the latest supported Node.js versions helps to minimize potential security vulnerabilities.

    To help our users understand our approach to Node.js version support, we have established a clear Node.js Version Support Policy for ts-graphviz.

    We encourage our users to update their projects to the latest LTS version of Node.js to ensure the best performance, security, and compatibility with ts-graphviz.

    Key Concepts

    ts-graphviz is a TypeScript library designed to create, manipulate, and render Graphviz DOT language graphs.

    It is built around several key concepts that make it modular, extensible, and easy to use:

    1. TypeScript-First Design & Type Definitions: ts-graphviz is designed with TypeScript as its primary language, providing strong typing and ensuring seamless integration with TypeScript projects. This enables users to leverage the full power of TypeScript's type system and tooling while working with Graphviz graphs. The library includes comprehensive type definitions for DOT language elements, making it easier to work with Graphviz elements in a type-safe manner.

    2. Object-Oriented API: ts-graphviz provides an object-oriented API for creating and manipulating graph elements like graphs, nodes, and edges. This enables users to work with complex graph structures intuitively and efficiently.

    3. Modular Design[New in v2]: The library is split into multiple packages, each serving a specific purpose. This modular design allows users to pick and choose the functionality they need, resulting in improved maintainability and flexibility.

    4. AST Support: ts-graphviz includes a module for processing DOT language at the Abstract Syntax Tree (AST) level. This feature allows users to parse and generate DOT language while preserving its structure, making it easier to manipulate and transform graphs programmatically.

    5. Runtime Adapter: The library provides adapter functions that enable users to execute Graphviz commands across different runtime environments, such as Node.js and Deno. These adapter functions serve as a wrapper, allowing for seamless integration with various platforms.

    6. Extensibility: ts-graphviz has been designed with extensibility in mind, allowing users to extend its functionality with custom implementations for specific use cases.

    7. Multi-Paradigm Support: ts-graphviz is designed to accommodate various programming paradigms, such as Object-Oriented Programming, Declarative Programming, and Functional Programming. This ensures that users can choose the programming style that best suits their needs and preferences, making it adaptable and versatile across different use cases and development approaches.

    By combining these key concepts, ts-graphviz aims to provide a powerful and user-friendly tool for working with Graphviz DOT language in TypeScript projects.

    What's changed?

    Package splitting and monorepo-ization

    Purpose

    The purpose of package splitting and monorepo-ization in the ts-graphviz v2 is to achieve the following objectives:

    • Improved modularity: By separating functionality into distinct packages, the library becomes more modular. This allows users to install and use only the specific components they need, reducing unnecessary dependencies and improving overall performance.
    • Easier maintainability: Splitting the library into smaller packages makes it easier for developers to maintain and update each package independently. This allows for faster bug fixes, feature enhancements, and more efficient development cycles.
    • Clearer dependencies: Package splitting results in a more explicit dependency structure between components, making it easier for developers to understand and manage dependencies within the project.
    • Increased flexibility: With a modular package structure, users can choose to use only the features they need, making it easier to integrate ts-graphviz into a broader range of projects and applications.
    • Simplified collaboration: By breaking down the library into separate packages within a monorepo, contributors can focus on specific areas of interest without interfering with other parts of the library. This facilitates collaboration and encourages more developers to contribute to the project.
    • Centralized management: Monorepo-ization allows for the centralized management of all the packages. This enables developers to track issues, manage pull requests, and maintain documentation in a single location, increasing efficiency and reducing overhead.
    • Consistent versioning and releases: Monorepo-ization ensures that versioning and release processes are consistent across all packages, making it easier to maintain and update the library as a whole.

    Overall, package splitting and monorepo-ization aim to create a more robust, maintainable, and user-friendly library that better serves the needs of the ts-graphviz community.

    Packages

    In v2 of ts-graphviz, the library functionality will be split into several packages. The packages to be split are as follows:

    • @ts-graphviz/common: Contains type information related to DOT language attributes, attribute values, and models.
    • @ts-graphviz/ast: Includes the module for processing DOT language at the AST (Abstract Syntax Tree) level.
    • @ts-graphviz/core: Comprises the implementation of models and functions provided to users.
    • @ts-graphviz/adapter: Handles runtime-dependent processing. For example, it provides I/O processing related to image generation in Graphviz on different runtimes, such as Node.js and Deno.

    To ensure that existing users are not affected, the ts-graphviz package will remain available. This change will result in a clear division of functionality and will improve the scalability and maintainability of the project. However, users of previous versions and users who wish to use the library without extending it will be able to continue to use the ts-graphviz package as is.

    • ts-graphviz: The main package that serves as the entry point for users. It provides a high-level API for creating, manipulating, and rendering Graphviz DOT language graphs. This package depends on the other packages to provide its functionality.

    Please note that while we strive to maintain compatibility, there might be some minor differences or limitations in the compatibility package compared to the original ts-graphviz library. It is essential to review the documentation and update your code accordingly if needed, but only when you decide to migrate to the new package structure.

    Dependency graph

    | Package | Summary | Description | | -------------------------------------------------------------------------- | ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ts-graphviz | Graphviz library for TypeScript | The main package that serves as the entry point for users. It provides a high-level API for creating, manipulating, and rendering Graphviz DOT language graphs. | | @ts-graphviz/common | Graphviz Types and Utilities | Contains type information related to DOT language attributes, attribute values, and models. | | @ts-graphviz/ast | Graphviz AST(Abstract Syntax Tree) Utilities | Includes the module for processing DOT language at the AST (Abstract Syntax Tree) level. | | @ts-graphviz/core | Graphviz Models for Object-Oriented Programming | Comprises the implementation of models and functions provided to users. | | @ts-graphviz/adapter | Graphviz Runtime adapters for Cross Platform | Handles runtime-dependent processing, such as input/output processing and Renderer implementations for different environments. |

    dependency-graph

    Node.js Version Support Update

    Starting with the upcoming release, ts-graphviz will no longer support Node.js 14 & 16, which has reached its End-of-Life (EOL). The new minimum guaranteed version will be Node.js 18. This decision allows us to focus on providing a secure and up-to-date library while minimizing the maintenance burden of supporting outdated versions.

    To minimize disruption for our users, we have established a clear Node.js Version Support Policy for our library. This policy helps users understand our approach to Node.js version support and what to expect when using our library.

    We encourage our users to update their projects to the latest LTS version of Node.js to ensure the best performance, security, and compatibility with ts-graphviz.

    Node.js Version Support Policy

    Our goal is to provide a stable and secure library for our users while keeping up with improvements in the JavaScript ecosystem. To achieve this, we have established the following Node.js version support policy for ts-graphviz:

    1. Minimum Guaranteed Version: We guarantee support for the latest Node.js version that has entered Long-Term Support (LTS) at the time of a major release of our library. This ensures that our library benefits from the stability and long-term support provided by LTS versions.

    2. End-of-Life (EOL) Policy: We will cease support for Node.js versions when they reach their EOL, as defined by the Node.js release schedule. This helps us focus on providing a secure and up-to-date library while minimizing the maintenance burden of supporting outdated versions.

    3. Version Support Communication: We will communicate our Node.js version support policy in our library's documentation and release notes. When a new major version is released or when a Node.js version enters EOL, we will inform our users through release notes, blog posts, or other relevant channels.

    4. Migration Guides : When introducing breaking changes due to Node.js version support updates, we will provide migration guides to help our users transition their projects to the new requirements smoothly.

    Migration Guides

    Update Node.js Version

    To migrate to the new Node.js version support policy, follow these steps:

    1. Check Node.js Version: First, check the version of Node.js used in your project by running the following command in your terminal:
      node -v
      
    2. Update Node.js: If your project is using Node.js 14 or 16, update it to the latest LTS version of Node.js (Node.js 18) by following the installation instructions provided on the official Node.js website or using a version manager like nvm or n.
    3. Update Dependencies: After updating Node.js, review your project's dependencies to ensure that they are compatible with the new Node.js version. Update any dependencies that require changes to work with the latest LTS version of Node.js.
    4. Test and Verify: Test your project with the updated Node.js version to ensure that it works as expected. Verify that all functionality is intact and that there are no compatibility issues with the new Node.js version.

    By following these steps, you can migrate your project to the latest LTS version of Node.js and ensure compatibility with ts-graphviz.

    Migrate AttributeKeyDict type to Attribute.keys type

    AttributeKeyDict was deprecated in v1, so it was removed in v2. Please modify to use Attribute.keys.

    - import { AttributeKeyDict } from 'ts-graphviz';
    + import { Attribute } from '@ts-graphviz/common';
    
    - const foo: AttributeKeyDict = ...;
    + const foo: Attribute.keys = ...;
    

    Migrate ts-graphviz/adapter to @ts-graphviz/adapter

    To migrate from the ts-graphviz/adapter module to the @ts-graphviz/adapter module, follow these steps:

    1. Update Import Statements: Update import statements in your code to use the new module name.

      - import { } from 'ts-graphviz/adapter';
      + import { } from '@ts-graphviz/adapter';
      
    2. Update Package.json: Update the ts-graphviz dependency in your package.json file to use the new version of the @ts-graphviz/adapter module.

      - "ts-graphviz": "^1.0.0",
      + "ts-graphviz": "^2.0.0",
      + "@ts-graphviz/adapter": "^2.0.0",
      
    3. Update Code References: Search your codebase for any references to the ts-graphviz/adapter module and update them to use the new module name.

      - import { } from 'ts-graphviz/adapter';
      + import { } from '@ts-graphviz/adapter';
      

    Migrate ts-graphviz/ast to @ts-graphviz/ast

    To migrate from the ts-graphviz/adapter module to the @ts-graphviz/adapter module, follow these steps:

    1. Update Import Statements: Update import statements in your code to use the new module name.

      - import { } from 'ts-graphviz/ast';
      + import { } from '@ts-graphviz/ast';
      
    2. Update Package.json: Update the ts-graphviz dependency in your package.json file to use the new version of the @ts-graphviz/ast module.

      - "ts-graphviz": "^1.0.0",
      + "ts-graphviz": "^2.0.0",
      + "@ts-graphviz/ast": "^2.0.0",
      
    3. Update Code References: Search your codebase for any references to the ts-graphviz/ast module and update them to use the new module name.

      - import { } from 'ts-graphviz/ast';
      + import { } from '@ts-graphviz/ast';
      

    Migrate Extending the Type System

    Common types moves to @ts-graphviz/common in v2.0.0.

    If you have extended the type system, you need to update the import path.

    Use Case: Specifying Custom Graph Layout and Output Formats
    -import { $keywords } from 'ts-graphviz';
    +import { $keywords } from '@ts-graphviz/common';
    -import { toFile } from 'ts-graphviz/adapter';
    +import { toFile } from '@ts-graphviz/adapter';
    
    -// 1. Declare the 'ts-graphviz/adapter' module.
    -declare module 'ts-graphviz/adapter' {
    +// 1. Declare the '@ts-graphviz/adapter' module.
    +declare module '@ts-graphviz/adapter' {
      export namespace Layout {
        // 2. Define the $values interface in the Layout namespace.
        // 3. Inherit from $keywords<'my-custom-algorithm'> and specify the name of the new layout engine in <...>.
        export interface $values extends $keywords<'my-custom-algorithm'> {}
      }
    
      export namespace Format {
        // 4. Define the $values interface in the Format namespace.
        // 5. Inherit from $keywords<'mp4'> and specify the name of the new output format in <...>.
        export interface $values extends $keywords<'mp4'> {}
      }
    }
    
    toFile('digraph { a -> b }', '/path/to/file', {
      layout: 'my-custom-algorithm',
      format: 'mp4',
    });
    
    Use Case: Adding Custom Attributes
    - import { digraph, toDot, attribute as _, $keywords } from 'ts-graphviz';
    + import {  $keywords } from '@ts-graphviz'/common;
    + import { digraph, toDot, attribute as _ } from 'ts-graphviz';
    
    -// 1. Declare the 'ts-graphviz' module.
    -declare module 'ts-graphviz' {
    +// 1. Declare the '@ts-graphviz/common' module.
    +declare module '@ts-graphviz/common' {
      export namespace GraphAttributeKey {
        // 2. Define the $values interface in the GraphAttributeKey namespace.
        // 3. Inherit from $keywords<'hoge'> and specify the name of the new attribute in <...>.
        export interface $values extends $keywords<'hoge'> {}
      }
    
      export namespace Attribute {
        // 4. Define the $keys interface in the Attribute namespace.
        // 5. Inherit from $keywords<'hoge'> and specify the name of the new attribute in <...>.
        export interface $keys extends $keywords<'hoge'> {}
    
        // 6. Define the $types interface in the Attribute namespace.
        // 7. Specify the new attribute in the key and define its corresponding value in the value.
        export interface $types {
          hoge: string;
        }
      }
    }
    
    console.log(
      toDot(
        digraph((g) => {
          g.set(_.hoge, 'fuga');
        }),
      ),
    );
    

    Development

    Package manager

    Migration from yarn v1 to pnpm has been done for package management.

    Build tool and Test suite

    To enhance the development experience, the build tool has been changed from rollup to vite, and the test suite from jest to vitest. This was done because jest lacked standard support for monorepo integration and TypeScript, requiring the installation of additional plugins. However, vite and vitest handle these challenges more elegantly, providing a smoother and more efficient development workflow.

    Release flow

    The release flow has been updated to use the changeset tool to manage changes and releases.

    This tool allows for a more streamlined and automated release process, making it easier to manage versioning and changelogs across multiple packages within the monorepo.

    Linter an Formatter

    The linter and formatter have been updated to use biome, respectively.

    This change was made to ensure consistent code style and formatting across the entire codebase, making it easier to maintain and contribute to the project.

    API Changes

    • The status of the ModelContext API and other APIs that were provided in beta and alpha have been removed. This is a temporary measure to ensure compliance with the @microsoft/api-extractor specification used internally in the d.ts file rollup.

Patch Changes

  • #966 d579034 Thanks @dependabot! - build(deps-dev): bump vite-plugin-dts from 3.7.2 to 3.7.3

  • #970 54f4565 Thanks @dependabot! - build(deps-dev): bump @types/node from 20.11.20 to 20.11.24

  • Updated dependencies [d579034, 54f4565, 1e4f57a]:

    • @ts-graphviz/core@2.0.0
    • @ts-graphviz/common@2.0.0
    • @ts-graphviz/ast@2.0.0
    • @ts-graphviz/adapter@2.0.0