Comfy-Org/ComfyUI_frontend
1
0
Fork 0
mirror of https://github.com/Comfy-Org/ComfyUI_frontend.git synced 2026-02-20 23:04:06 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
c8bcbc06e4288cd03301b6f83c9117e8ff190949
ComfyUI_frontend/docs/adr/0002-monorepo-conversion.md
snomiao b4b834d7c4 [chore] Replace pnpm with npm package manager 
- Remove pnpm-specific files (pnpm-lock.yaml, pnpm-workspace.yaml)
- Update package.json scripts to use npm instead of pnpm
- Add npm workspaces configuration
- Update all GitHub workflow files to use npm
- Update documentation to reference npm commands
- Generate package-lock.json for npm dependency management
2025-08-31 05:41:12 +00:00

1.6 KiB
Raw 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

  • 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

npm 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