Comfy-Org/ComfyUI_frontend
1
0
Fork 0
mirror of https://github.com/Comfy-Org/ComfyUI_frontend.git synced 2026-02-28 10:44:12 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
962302d5ba0a238f8fd3e49af53f3d41f09a8a28
ComfyUI_frontend/CLAUDE.md
Rizumu Ayaka 3895a43b73 feat: v3 style of node body (#5169) 
* feat: v3 style of node body

* Update src/renderer/extensions/vueNodes/components/LGraphNode.vue

* fix: review's issues

* fix: review's issue
2025-08-22 21:49:13 -07:00

2.0 KiB
Raw Blame History

ComfyUI Frontend Project Guidelines

Quick Commands

  • npm run: See all available commands
  • npm run typecheck: Type checking
  • npm run lint: Linting
  • npm run format: Prettier formatting
  • npm run test:component: Run component tests with browser environment
  • npm run test:unit: Run all unit tests
  • npm run test:unit -- tests-ui/tests/example.test.ts: Run single test file

Development Workflow

  1. Make code changes
  2. Run tests (see subdirectory CLAUDE.md files)
  3. Run typecheck, lint, format
  4. Check README updates
  5. Consider docs.comfy.org updates

Git Conventions

  • Use [prefix] format: [feat], [bugfix], [docs]
  • Add "Fixes #n" to PR descriptions
  • Never mention Claude/AI in commits

External Resources

Project Philosophy

  • Clean, stable public APIs
  • Domain-driven design
  • Thousands of users and extensions
  • Prioritize clean interfaces that restrict extension access

Repository Navigation

  • Check README files in key folders (tests-ui, browser_tests, composables, etc.)
  • Prefer running single tests for performance
  • Use --help for unfamiliar CLI tools

GitHub Integration

When referencing Comfy-Org repos:

  1. Check for local copy
  2. Use GitHub API for branches/PRs/metadata
  3. Curl GitHub website if needed

Common Pitfalls

  • NEVER use any type - use proper TypeScript types
  • NEVER use as any type assertions - fix the underlying type issue
  • NEVER use --no-verify flag when committing
  • NEVER delete or disable tests to make them pass
  • NEVER circumvent quality checks
  • NEVER use dark: prefix - always use dark-theme: for dark mode styles, for example: dark-theme:text-white dark-theme:bg-black
  • NEVER use :class="[]" to merge class names - always use import { cn } from '@/utils/tailwindUtil', for example: <div :class="cn('bg-red-500', { 'bg-blue-500': condition })" />