From df1fb8ba6fe990e6c07be5fba2f9692c07886979 Mon Sep 17 00:00:00 2001 From: Kyle Mathews Date: Tue, 14 Sep 2021 15:53:47 -0700 Subject: [PATCH] fix(gatsby-source-drupal): check relationships type exists on node before filtering (#33181) * fix(gatsby-source-drupal): check relationships type exists on node before filtering * Update packages/gatsby-source-drupal/src/utils.js Co-authored-by: Dustin Schau * format Co-authored-by: Dustin Schau --- packages/gatsby-source-drupal/src/utils.js | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/packages/gatsby-source-drupal/src/utils.js b/packages/gatsby-source-drupal/src/utils.js index ed19cbca059b1..1103a2ccff49e 100644 --- a/packages/gatsby-source-drupal/src/utils.js +++ b/packages/gatsby-source-drupal/src/utils.js @@ -4,7 +4,6 @@ const { nodeFromData, downloadFile, isFileNode, - getHref, createNodeIdWithVersion, } = require(`./normalize`) @@ -262,10 +261,15 @@ ${JSON.stringify(nodeToUpdate, null, 4)} const nodeFieldName = `${newNode.internal.type}___NODE` removedReferencedNodes.forEach(referencedNode => { - referencedNode.relationships[nodeFieldName] = - referencedNode.relationships[nodeFieldName].filter( - id => id !== newNode.id - ) + if ( + referencedNode.relationships && + referencedNode.relationships[nodeFieldName] + ) { + referencedNode.relationships[nodeFieldName] = + referencedNode.relationships[nodeFieldName].filter( + id => id !== newNode.id + ) + } }) // see what nodes are newly referenced, and make sure to call `createNode` on them