The Comfy-Org fork of litegraph.js has been merged into the ComfyUI Frontend repository and is no longer maintained here.

Open
#1,196 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
5/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
typescript

Research direction

No implementation work remains in this repository: the Comfy-Org/litegraph.js fork was merged into ComfyUI Frontend and archived. Read the linked ADR-0001 and merge PR #4667 for the migration context; active development and issue reports belong in ComfyUI_frontend, while this issue documents the final release and deprecation.

Written by the indexing model from the issue text.

Description

announcement

The Comfy-Org fork of litegraph.js (@comfyorg/litegraph) has been merged into the ComfyUI Frontend repository and is no longer maintained here.

Important Note

This archival only affects the Comfy-Org/litegraph.js fork. The original litegraph.js repository remains separate and unaffected by this change.

Quick Links
For developers using @comfyorg/litegraph
  • The npm package @comfyorg/litegraph is deprecated
  • This fork was specifically maintained for ComfyUI and had no other known users
  • All ComfyUI-specific enhancements and fixes are now in the ComfyUI Frontend repository
  • Import paths have changed from @comfyorg/litegraph to @/lib/litegraph within ComfyUI
Why was this archived?

The Comfy-Org fork of litegraph.js was created specifically for ComfyUI's needs. Since ComfyUI was the only consumer of this fork, maintaining it as a separate package added unnecessary complexity. The integration enables better architectural decisions and faster development.

Repository Status
  • ✅ All git history has been preserved via git subtree merge
  • ✅ All open issues have been transferred to ComfyUI Frontend
  • ✅ A final release (v0.8.7) has been published marking the deprecation
  • 🚫 No new commits, issues, or PRs will be accepted here
  • 🚫 Open PRs (20) will need to be manually transferred

This issue will remain pinned for visibility. The repository is archived to preserve history but prevent confusion about where active development occurs.

Dominant language
TypeScript
Stars
256
Forks
66
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.