Plugin option filter is unnamed ${test.toString()} ${proce

Error message

Plugin option filter is unnamed

${test.toString()}

${processor.toString()}

What it means

Error "Plugin option filter is unnamed ${test.toString()} ${processor.toString()}" thrown in gatsbyjs/gatsby.

Source

Thrown at packages/gatsby-source-wordpress/src/steps/process-and-validate-plugin-options.ts:146

            )
          )
        }
      })

      return userPluginOptions
    },
  },
]

export const processAndValidatePluginOptions = (
  helpers: GatsbyNodeApiHelpers,
  pluginOptions: IPluginOptions
): IPluginOptions => {
  let userPluginOptions = cloneDeep(pluginOptions)

  optionsProcessors.forEach(({ test, processor, name }) => {
    if (!name) {
      helpers.reporter.panic(
        formatLogMessage(
          `Plugin option filter is unnamed\n\n${test.toString()}\n\n${processor.toString()}`
        )
      )
    }

    if (test({ helpers, userPluginOptions })) {
      const filteredUserPluginOptions = processor({
        helpers,
        userPluginOptions,
      })

      if (filteredUserPluginOptions) {
        userPluginOptions = filteredUserPluginOptions
      } else {
        helpers.reporter.panic(
          formatLogMessage(
            `Plugin option filter ${name} didn't return a filtered options object`

View on GitHub (pinned to 8b06340921)

Solutions

Give the plugin option filter a name property in your gatsby-config.js plugin options filters.
Ensure every filter in the options.filters array includes { name, test, processor }.

When it happens

Trigger: Thrown at packages/gatsby-source-wordpress/src/steps/process-and-validate-plugin-options.ts:146 when the library encounters an invalid state.

Common situations: Occurs when a plugin option filter is defined without a name. Give each filter in the plugin options a `name` property so failures can be identified.

AI-assisted analysis of gatsbyjs/gatsby@8b06340921 (2026-08-13). Data as JSON: /api/errors/6ae0ee5d3f798202. Report an issue: GitHub.