gatsbyjs/gatsby · error · Error
No response or non 200 code for ${url}
Error message
No response or non 200 code for ${url} What it means
check-deps-changes GETs the package.json of the installed dependency version from unpkg.com to compare against the local one; a missing response or non-200 status code throws here. The URL is constructed from packageName@version, so an unpublished/removed version or network failure triggers it.
Source
Thrown at packages/gatsby-dev-cli/src/utils/check-deps-changes.js:67
)
return {
didDepsChanged: false,
packageNotInstalled,
}
}
// if package is not installed, we will do http GET request to
// unkpg to check if dependency in package published in public
// npm repository are different
// this allow us to not publish to local repository
// and save some time/work
try {
const version = getPackageVersion(packageName)
const url = `https://unpkg.com/${packageName}@${version}/package.json`
const response = await got(url)
if (response?.statusCode !== 200) {
throw new Error(`No response or non 200 code for ${url}`)
}
localPKGjson = JSON.parse(response.body)
} catch (e) {
console.log(
`'${packageName}' doesn't seem to be installed and is not published on NPM. Error: ${e.message}`
)
return {
didDepsChanged: true,
packageNotInstalled,
}
}
}
const monoRepoPackageJsonPath = getMonorepoPackageJsonPath({
packageName,
packageNameToPath,
})
const monorepoPKGjsonString = fs.readFileSync(View on GitHub (pinned to e85d62f177)
Solutions
- Check the package version exists on npm/unpkg (not unpublished)
- Retry when the network or unpkg is temporarily unavailable
- Ensure the local package.json version string is valid
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at packages/gatsby-dev-cli/src/utils/check-deps-changes.js:67 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/1d878ab7bca34276.
Report an issue: GitHub.