gatsbyjs/gatsby · error

There were ${mimeTypeExcluded} files with mime types that we

Error message

There were ${mimeTypeExcluded} files with mime types that were included in the excludeByMimeTypes config option and consequently were not fetched. Visit https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-source-wordpress/docs/debugging-and-troubleshooting.md#media-file-download-skipped for more info.

What it means

In logPostBuildWarnings, this fires when files were excluded from fetching because their mime types matched the excludeByMimeTypes plugin option. It reports the excluded count post-build; the skip is by configuration, not an error, so builds succeed while those media files have no local file nodes.

Source

Thrown at packages/gatsby-source-wordpress/src/steps/log-post-build-warnings.ts:30

  const helpUrl = `https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-source-wordpress/docs/debugging-and-troubleshooting.md#media-file-download-skipped`

  const helpText = `Visit ${helpUrl} for more info.`

  if (maxFileSizeBytesExceeded > 0) {
    const message = formatLogMessage(
      `There were ${maxFileSizeBytesExceeded} files with file sizes that are above the maxFileSizeBytes config option and consequently were not fetched. ${helpText}`
    )

    reporter.warn(message)
  }

  if (mimeTypeExcluded > 0) {
    const message = formatLogMessage(
      `There were ${mimeTypeExcluded} files with mime types that were included in the excludeByMimeTypes config option and consequently were not fetched. ${helpText}`
    )

    reporter.warn(message)
  }
}

View on GitHub (pinned to e85d62f177)

Solutions

  1. Remove or adjust the excludeByMimeTypes list in plugin options if those files should be fetched.
  2. Keep the option if exclusion is intentional; the warning is informational.
  3. Use the linked troubleshooting doc to audit which mime types are being skipped.
Defensive patterns

Strategy: validation

When it happens

Trigger: Thrown at packages/gatsby-source-wordpress/src/steps/log-post-build-warnings.ts:30 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/3db31a77ab8c2b67. Report an issue: GitHub.