Enforce correct package naming convention for n8n community nodes (`@n8n/community-nodes/package-name-convention`)

💼 This rule is enabled in the following configs: ✅ recommended, ☑️ recommendedWithoutN8nCloudSupport.

💡 This rule is manually fixable by editor suggestions.

Rule Details

Validates that your package name follows the correct n8n community node naming convention. Package names must start with n8n-nodes- and can optionally be scoped.

Examples

❌ Incorrect

{
  "name": "my-service-integration"
}

{
  "name": "nodes-my-service"
}

{
  "name": "@company/my-service"
}

✅ Correct

{
  "name": "n8n-nodes-my-service"
}

{
  "name": "@company/n8n-nodes-my-service"
}

Best Practices

Use descriptive service names: n8n-nodes-github rather than n8n-nodes-api
For company packages, use your organization scope: @mycompany/n8n-nodes-internal-tool

1.1 KiB Raw Blame History

Enforce correct package naming convention for n8n community nodes (@n8n/community-nodes/package-name-convention)