feat: Send node execution finished and node execution data in separate events (no-changelog) (#18875)

Co-authored-by: Tomi Turtiainen <10324676+tomi@users.noreply.github.com>

packages/@n8n/api-types/src/push/execution.ts

@@ -52,23 +52,36 @@ export type NodeExecuteBefore = {
 	};
 };
 
+/**
+ * Message sent after a node has finished executing that contains all that node's data
+ * except for the output items which are sent in the `NodeExecuteAfterData` message.
+ */
 export type NodeExecuteAfter = {
 	type: 'nodeExecuteAfter';
 	data: {
 		executionId: string;
 		nodeName: string;
-		data: ITaskData;
+		data: Omit<ITaskData, 'data'>;
+		itemCount: number;
+	};
+};
 
+/**
+ * Message sent after a node has finished executing that contains the entire output data
+ * of that node. This is sent immediately after `NodeExecuteAfter`.
+ */
+export type NodeExecuteAfterData = {
+	type: 'nodeExecuteAfterData';
+	data: {
+		executionId: string;
+		nodeName: string;
 		/**
 		 * When a worker relays updates about a manual execution to main, if the
 		 * payload size is above a limit, we send only a placeholder to the client.
 		 * Later we fetch the entire execution data and fill in any placeholders.
-		 *
-		 * When sending a placheolder, we also send the number of output items, so
-		 * the client knows ahead of time how many items are there, to prevent the
-		 * items count from jumping up when the execution finishes.
 		 */
-		itemCount?: number;
+		data: ITaskData;
+		itemCount: number;
 	};
 };
 
@@ -78,4 +91,5 @@ export type ExecutionPushMessage =
 	| ExecutionFinished
 	| ExecutionRecovered
 	| NodeExecuteBefore
-	| NodeExecuteAfter;
+	| NodeExecuteAfter
+	| NodeExecuteAfterData;