Comfy-Org/ComfyUI_frontend
1
0
Fork 0
mirror of https://github.com/Comfy-Org/ComfyUI_frontend.git synced 2026-02-03 22:59:14 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
perf/code-split-xterm-cloud
ComfyUI_frontend/docs/adr/0002-monorepo-conversion.md
Alexander Brown aa5125cef6 Chore: Oxfmt formatting pass (#8341) 
## Summary

Expanding the covered files to format. One-time formatting pass. To be
added to the `.git-blame-ignore-revs`

┆Issue is synchronized with this [Notion
page](https://www.notion.so/PR-8341-Chore-Oxfmt-formatting-pass-2f56d73d365081f2988fcb7570f9a2a1)
by [Unito](https://www.unito.io)
2026-01-27 17:59:19 -08:00

1.6 KiB
Raw Permalink Blame History

2. Restructure ComfyUI_frontend as a monorepo

Date: 2025-08-25

Status

Proposed

Context

Most of the context is in here

TL;DR: As we're merging more subprojects like litegraph, devtools, and soon a fork of PrimeVue, a monorepo structure will help a lot with code sharing and organization.

For more information on Monorepos, check out monorepo.tools

Decision

  • Swap out NPM for PNPM
  • Add a workspace for the PrimeVue fork
  • Move the frontend code into its own app workspace
  • Longer term: Extract and reorganize common infrastructure to take advantage of the new monorepo tooling

Tools proposed

PNPM and PNPM workspaces

For monorepo management, I'd probably go with Nx, but I could be conviced otherwise. There's a whole list here if you're interested.

Consequences

Positive

  • Adding new projects with shared dependencies becomes really easy
  • Makes the process of forking and customizing projects more structured, if not strictly easier
  • It could speed up the build and development process (not guaranteed)
  • It would let us cleanly organize and release packages like comfyui-frontend-types

Negative

  • Monorepos take some getting used to
  • Reviews and code contribution management has to account for the different projects' situations and constraints