serverless/serverless · error · ServerlessError

CONFIGURATION_PARSE_ERROR

CONFIGURATION_PARSE_ERROR

Error message

Cannot parse "${path.basename(configurationPath)}": ${error.message}

What it means

Error "Cannot parse "${path.basename(configurationPath)}": ${error.message}" thrown in serverless/serverless.

Source

Thrown at packages/serverless/lib/configuration/read.js:52

    throw new ServerlessError(
      `Cannot parse "${path.basename(configurationPath)}": ${error.message}`,
      'CONFIGURATION_NOT_ACCESSIBLE',
    )
  }
}

const parseConfigurationFile = async (configurationPath) => {
  switch (path.extname(configurationPath)) {
    case '.yml':
    case '.yaml': {
      const content = await readConfigurationFile(configurationPath)
      try {
        return yaml.load(content, {
          filename: configurationPath,
          schema: cloudformationSchema,
        })
      } catch (error) {
        throw new ServerlessError(
          `Cannot parse "${path.basename(configurationPath)}": ${
            error.message
          }`,
          'CONFIGURATION_PARSE_ERROR',
        )
      }
    }
    case '.json': {
      const content = await readConfigurationFile(configurationPath)
      try {
        return JSON.parse(content)
      } catch (error) {
        throw new ServerlessError(
          `Cannot parse "${path.basename(
            configurationPath,
          )}": JSON parse error: ${error.message}`,
          'CONFIGURATION_PARSE_ERROR',
        )

View on GitHub (pinned to b9d7ea51c8)

Solutions

1. Address the parse error shown for the configuration file (invalid syntax or unsupported content) and retry.

When it happens

Trigger: Thrown at packages/serverless/lib/configuration/read.js:52 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of serverless/serverless@b9d7ea51c8 (2026-08-13). Data as JSON: /api/errors/25cf752c4f351f90. Report an issue: GitHub.