GoogleChrome/lighthouse · error · Error
${pluginName} has unrecognized ${objectName}properties: [${k
Error message
${pluginName} has unrecognized ${objectName}properties: [${keys}] What it means
Error "${pluginName} has unrecognized ${objectName}properties: [${keys}]" thrown in GoogleChrome/lighthouse.
Source
Thrown at core/config/config-plugin.js:59
return arr.every(objectIsGatherMode);
}
/**
* Asserts that obj has no own properties, throwing a nice error message if it does.
* Plugin and object name are included for nicer logging.
* @param {Record<string, unknown>} obj
* @param {string} pluginName
* @param {string=} objectName
*/
function assertNoExcessProperties(obj, pluginName, objectName = '') {
if (objectName) {
objectName += ' ';
}
const invalidKeys = Object.keys(obj);
if (invalidKeys.length > 0) {
const keys = invalidKeys.join(', ');
throw new Error(`${pluginName} has unrecognized ${objectName}properties: [${keys}]`);
}
}
/**
* A set of methods for extracting and validating a Lighthouse plugin config.
*/
class ConfigPlugin {
/**
* Extract and validate the list of AuditDefns added by the plugin (or undefined
* 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;View on GitHub (pinned to 9515cd4e58)
Solutions
- Remove the unrecognized properties from the plugin object.
- Check the plugin documentation for the list of supported properties (audits, category, groups, supportedModes).
When it happens
Trigger: Thrown when a plugin object contains properties Lighthouse does not recognize.
Common situations: See trigger scenarios.
AI-assisted analysis of GoogleChrome/lighthouse@9515cd4e58 (2026-08-13).
Data as JSON: /api/errors/a0e859cf36d7a43f.
Report an issue: GitHub.