eyaltoledano/claude-task-master · warning

...and ${invalidDependencies.length - 5} more

Error message

  ...and ${invalidDependencies.length - 5} more

What it means

Truncation notice from displayInvalidDependencyWarnings: when more than 5 invalid dependency references exist, only the first 5 are printed and this line reports the remaining count. Purely cosmetic throttling of warning output.

Source

Thrown at apps/cli/src/commands/list.command.ts:506

		tagName?: string
	): void {
		if (invalidDependencies.length === 0) {
			return;
		}

		const tagContext = tagName ? ` (tag: ${tagName})` : '';
		console.warn(
			chalk.yellow(
				`\nWarning: ${invalidDependencies.length} invalid dependency reference(s) found${tagContext}:`
			)
		);
		invalidDependencies.slice(0, 5).forEach(({ taskId, depId }) => {
			console.warn(
				chalk.gray(`  Task ${taskId} depends on non-existent task ${depId}`)
			);
		});
		if (invalidDependencies.length > 5) {
			console.warn(
				chalk.gray(`  ...and ${invalidDependencies.length - 5} more`)
			);
		}
	}

	/**
	 * Display results based on format
	 */
	private displayResults(
		result: ListTasksResult,
		options: ListCommandOptions
	): void {
		// Resolve format: --json and --compact flags override --format option
		let format: OutputFormat = options.format || 'text';
		if (options.json) {
			format = 'json';
		} else if (options.compact) {
			format = 'compact';

View on GitHub (pinned to c0c98d367c)

Solutions

1. Run an automated dependency repair/prune pass to clean all invalid references at once.
2. Audit tasks.json for references to deleted task IDs, not just the 5 shown.
3. Recreate missing tasks in bulk if the dependencies are still semantically valid.

// Don't rely on the truncated CLI output — count all dangling refs yourself
const dangling = findDanglingDeps(tasks);
if (dangling.length > 5) {
  console.log(`Full list (${dangling.length}):`, JSON.stringify(dangling, null, 2));
}

When it happens

Trigger: Same flow as 705/706, but with invalidDependencies.length > 5 — i.e. six or more dangling dependency references in the loaded task set.

Common situations: Bulk deletion of tasks (e.g. removing a whole feature) leaving many dangling references; large imports with ID collisions; long-neglected tasks.json with accumulating integrity issues.

Related errors

• Warning: ${invalidDependencies.length} invalid dependency re
• Task ${taskId} depends on non-existent task ${depId}
• {"warning":"${message}"}
• ⚠️ ${message}
• Warning: Could not fetch tasks from ${failedTags.length} tag

AI-assisted analysis of eyaltoledano/claude-task-master@c0c98d367c (2026-08-29). Data as JSON: /api/errors/acb2f610275a3bd4. Report an issue: GitHub.