Why Does Installing My Community Node Create Duplicate ScrapeNinja Nodes?

Based on our documentation on community nodes, seeing duplicate nodes when installing a community node is not a bug in n8n core. Instead, it happens when two node definitions share the same name and icon. n8n displays community node entries by their name and icon in the Nodes panel, so if two nodes (even coming from the same package) have identical identifiers, they look exactly the same.

Here are a few things to check in your module:

• Node Definition Names: Ensure that your node definitions (usually specified in the properties like displayName) are uniquely named if you intend to have only one node.
• Node Icon: If you want to differentiate nodes that might share a similar name, consider assigning unique icons to avoid confusion in the Nodes panel.

From the usage documentation, it’s clear that the duplicate naming issue is a known behavior. If your package intentionally exports multiple nodes with the same name, then this behavior is expected. Otherwise, reviewing your node code for duplicate names might be the next step.

If after checking your code you still encounter unexpected behavior, you may want to share additional details with the community for further insights.