GoogleChrome/lighthouse · error · Error

${pluginName} has a missing audit path.

Error message

${pluginName} has a missing audit path.

What it means

Error "${pluginName} has a missing audit path." thrown in GoogleChrome/lighthouse.

Source

Thrown at core/config/config-plugin.js:87

   * if no additional audits are being added by the plugin).
   * @param {unknown} auditsJson
   * @param {string} pluginName
   * @return {Array<{path: string}>|undefined}
   */
  static _parseAuditsList(auditsJson, pluginName) {
    // Plugin audits aren't required (relying on LH default audits) so fall back to [].
    if (auditsJson === undefined) {
      return undefined;
    } else if (!isArrayOfUnknownObjects(auditsJson)) {
      throw new Error(`${pluginName} has an invalid audits array.`);
    }

    return auditsJson.map(auditDefnJson => {
      const {path, ...invalidRest} = auditDefnJson;
      assertNoExcessProperties(invalidRest, pluginName, 'audit');

      if (typeof path !== 'string') {
        throw new Error(`${pluginName} has a missing audit path.`);
      }
      return {
        path,
      };
    });
  }

  /**
   * Extract and validate the list of category AuditRefs added by the plugin.
   * @param {unknown} auditRefsJson
   * @param {string} pluginName
   * @return {Array<LH.Config.AuditRefJson>}
   */
  static _parseAuditRefsList(auditRefsJson, pluginName) {
    if (!isArrayOfUnknownObjects(auditRefsJson)) {
      throw new Error(`${pluginName} has no valid auditsRefs.`);
    }

View on GitHub (pinned to 9515cd4e58)

Solutions

1. Add a `path` property to each entry in the plugin's audits array.
2. Ensure the path points to the audit implementation file within the plugin package.

When it happens

Trigger: Thrown when a plugin audit entry is missing its path to the audit implementation.

Common situations: See trigger scenarios.

AI-assisted analysis of GoogleChrome/lighthouse@9515cd4e58 (2026-08-13). Data as JSON: /api/errors/29f23837f572c7d3. Report an issue: GitHub.