A custom node's own range decides the packages it names

TripoSR's checkpoint loads with transformers 4, and ComfyUI runs 5: of a
package a node names, its range decides, and of everything else what
ComfyUI runs.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Ilker ManapandClaude Opus 5.5 committed 2026-10-10 18:54:15 +02:00
1 parent 4b68328e3e
commit dfc2f0bf15
6 files changed
+51 -11

No files matched your search

+5 -4
View File
@@ -564,10 +564,11 @@ type CustomNode struct {
// Commit is the full commit the node is used at: a branch moves, and a
// node that changed under a model is a model that changed unasked.
Commit string `json:"commit" koanf:"commit"`
// Requirements are the PyPI packages the node needs that ComfyUI does
// not have, by name and version range only. They are installed beside
// the replica, never into ComfyUI's environment, at the versions that
// environment already has of anything it shares.
// Requirements are the PyPI packages the node needs, by name and version
// range only. They are installed beside the replica, never into
// ComfyUI's environment: a package named here at the range named, and
// every other one at the version ComfyUI already runs. One named here
// is first on ComfyUI's path, so its range must suit ComfyUI too.
Requirements []string `json:"requirements,omitempty" koanf:"requirements"`
}