Suggestion for Node Package Management
- Dominant language
- Python
- Stars
- 133k
- Forks
- 15.7k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 155
Description
### Feature Idea
Hi ComfyUI Team,
First of all, thank you for the amazing work on ComfyUI!
I’d like to suggest a feature to improve performance and usability: adding an option to load nodes in packages instead of loading everything at once. For example:
When working with image workflows, only load image-related node packages (or pre-defined sets).
Similarly, load specific packages for tasks like text handling, audio training, etc.
A user interface could allow customization of these packages, or there could be an option to load only the nodes required by the current workflow. This would help reduce application overhead and make it easier to manage nodes based on specific use cases.
Hope this suggestion helps enhance the experience for users dealing with complex workflows!
Thanks!
### Existing Solutions
_No response_
### Other
_No response_
Contributor guide
Research direction
The issue identifies no files, tests, or entry points. Start by mapping how ComfyUI currently loads nodes and whether the current workflow can identify the nodes it requires. Before implementation, define package boundaries, customization behavior, and what successful selective loading should look like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100