fix: correct NodeConnectionType import to NodeConnectionTypes #94
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
NodeConnectionType(a type) was being importedinstead of
NodeConnectionTypes(the actual constant)ExampleNodeandHttpBinnodes to use the correct importProblem
The nodes were trying to use
NodeConnectionType.Mainwhich caused theTypeScript error:
'NodeConnectionType' only refers to a type, but is being used as a value hereSolution
Changed the import from
NodeConnectionTypetoNodeConnectionTypes(with an's') which is the actual exported constant from n8n-workflow.
Files changed
nodes/ExampleNode/ExampleNode.node.tsnodes/HttpBin/HttpBin.node.tsNote
Replace NodeConnectionType with NodeConnectionTypes and update inputs/outputs in both nodes.
nodes/ExampleNode/ExampleNode.node.tsandnodes/HttpBin/HttpBin.node.ts:NodeConnectionType->NodeConnectionTypes.inputs/outputsto useNodeConnectionTypes.Main.Written by Cursor Bugbot for commit 2e709b1. This will update automatically on new commits. Configure here.