gatsbyjs/gatsby · error

${e}

Error message

${e}

What it means

In createLocalFileNode, when hard-caching media files is enabled, the downloaded file is copied into the hard-cache directory; a throw from ensureDir/copyFile is escalated via reporter.panic with the original error. The input at fault is the local hard-cache path or disk state, not the remote file.

Source

Thrown at packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js:367

  }

  // push it's id and url to our store for caching,
  // so we can touch this node next time
  // and so we can easily access the id by source url later
  getStore().dispatch.imageNodes.pushNodeMeta({
    id: remoteFileNode.id,
    sourceUrl: mediaItemUrl,
    modifiedGmt,
  })

  if (hardCacheMediaFiles) {
    try {
      // make sure the directory exists
      await fs.ensureDir(path.dirname(hardCachedFilePath))
      // copy our downloaded file to our existing directory
      await fs.copyFile(remoteFileNode.absolutePath, hardCachedFilePath)
    } catch (e) {
      helpers.reporter.panic(e)
    }
  }

  // and use it
  return remoteFileNode
}

View on GitHub (pinned to e85d62f177)

Solutions

1. Check permissions/disk space for the hard-cache directory
2. Delete the hard-cache directory and rebuild
3. Disable hardCacheMediaFiles if the cache target is unreliable

When it happens

Trigger: Thrown at packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js:367 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of gatsbyjs/gatsby@e85d62f177 (2026-08-26). Data as JSON: /api/errors/f217aef725e38945. Report an issue: GitHub.