mirror of https://github.com/hanzo-studio/studio-frontend.git synced 2026-10-30 18:55:56 +00:00

Files

T

zeekay 17c510df79 Complete rebrand from ComfyUI to Hanzo Studio

- Replace all ComfyUI references with Hanzo Studio
- Update comfy.org URLs to hanzo.ai/studio.hanzo.ai
- Change comfyanonymous to hanzoai
- Update Comfy-Org to hanzo-studio
- Rename files and directories
- Update package names and configurations
- Update documentation and README files

This is a comprehensive rebranding to align with Hanzo AI's
product suite and company identity.

2025-11-23 20:50:10 -08:00

1.7 KiB

Raw Permalink Blame History

2. Restructure studio-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 hanzo-studio-frontend-types

Negative

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

1.7 KiB Raw Permalink Blame History