alighasami
3d5eaf9445
Security: Sync from Public / sync-from-public (push) Has been cancelled
Test: Benchmark Nightly / build (push) Has been cancelled
Test: Benchmark Nightly / Notify Cats on failure (push) Has been cancelled
CI: Python / Checks (push) Has been cancelled
Test: Evals Python / Workflow Comparison Python (push) Has been cancelled
Util: Check Docs URLs / check-docs-urls (push) Has been cancelled
Test: Visual Storybook / Cloudflare Pages (push) Has been cancelled
Test: E2E Performance / build-and-test-performance (push) Has been cancelled
Test: Workflows Nightly / Run Workflow Tests (push) Has been cancelled
Util: Cleanup CI Docker Images / Delete stale CI images (push) Has been cancelled
Test: Benchmark Destroy Env / build (push) Has been cancelled
Util: Update Node Popularity / update-popularity (push) Has been cancelled
Test: E2E Coverage Weekly / Coverage Tests (push) Has been cancelled
1.1 KiB
1.1 KiB
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-githubrather thann8n-nodes-api - For company packages, use your organization scope:
@mycompany/n8n-nodes-internal-tool