Community node descriptions now require both icon and subtitle
A new ESLint rule catches community nodes missing required `icon` or `subtitle` fields in their descriptions — both mandatory for the n8n marketplace.
Community nodes published to the n8n marketplace must include specific metadata so users understand what each node does. The icon field lets nodes display a custom icon in the workflow editor, while subtitle shows dynamic information like the operation being performed.
Previously, an ESLint rule enforced only the icon field. The subtitle field was required by marketplace review standards but only caught during human code review. A new rule now validates both fields automatically — developers see errors immediately in their IDE instead of waiting for reviewer feedback.
The old node-class-description-icon-missing rule is deprecated with ESLint's official deprecation metadata, directing users to the new rule. Both recommended and recommendedWithoutN8nCloudSupport ESLint configs have been updated to use the new rule.
In the @n8n/eslint-plugin-community-nodes plugin, developers writing .node.ts files will now see clear errors when either field is missing from their node class description.
View Original GitHub Description
Summary
Add a new ESLint rule require-node-description-fields to @n8n/eslint-plugin-community-nodes that validates community node class descriptions contain icon and subtitle. These fields are optional in the TypeScript interface but required by community node review standards — other required fields (displayName, name, group, version, description, etc.) are already enforced by tsc.
This supersedes the existing node-class-description-icon-missing rule (which only checked for icon) and marks it as deprecated with proper ESLint deprecation metadata.
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/CE-732
Review / Merge checklist
- I have seen this code, I have run this code, and I take responsibility for this code.
- PR title and summary are descriptive. (conventions)
- Docs updated or follow-up ticket created.
- Tests included.
- PR Labeled with
Backport to Beta,Backport to Stable, orBackport to v1(if the PR is an urgent fix that needs to be backported)