Add Gatsby image validation check

[KatalKavya96]

Description

This PR fixes #7650

This PR adds a Gatsby image validation guardrail through a new make check-images target.

The validation script scans Gatsby/React source files and reports <GatsbyImage /> components that are missing an explicit image prop. It supports both full project validation and scoped validation for a specific folder or file.

Example:

make check-images
make check-images -- src/pages/community

If missing image props are found, the command prints the file path and location, then exits with code 1.

Notes for Reviewers

Changes made:

• Added scripts/find-missing-gatsby-images.js
• Added check:images npm script
• Added check-images Makefile target
• Added support for scoped checks using folder/file paths

Tested with:

npm run check:images
make check-images
make check-images -- src/pages/community

Also manually tested with a temporary invalid <GatsbyImage /> missing the image prop, and the script correctly reported the issue with exit code 1.

Signed commits

• Yes, I signed my commits.

[github-actions]

🚀 Preview deployment: https://layer5.io/pr-preview/pr-7782/

Note: Preview may take a moment (GitHub Pages deployment in progress). Please wait and refresh. Track deployment here

[KatalKavya96]

@lekaf974

[Junnygram]

I have two minor suggestions to make it more robust:

1. False Positives on Spreads: In hasImageProp, if a developer uses a spread operator (<GatsbyImage {...props} />), the attribute type is JSXSpreadAttribute, meaning attribute.name is undefined. The script currently flags these as failures. You might want to update the logic to return true (or skip validation) if attributes.some(attr => attr.type === 'JSXSpreadAttribute') is found, to prevent false positives.
2. Dependencies: The script directly requires @babel/parser and @babel/traverse, but I don't see them added to package.json. Even if they are hoisted by Gatsby, it's best practice to explicitly add them to devDependencies to prevent "phantom dependency" issues on fresh installs in the future.

[KatalKavya96]

@Junnygram Updated the PR based on the suggestions:

• Added handling for JSXSpreadAttribute so usages like <GatsbyImage {...props} /> are not incorrectly flagged as missing the image prop.

• Added @babel/parser and @babel/traverse explicitly to devDependencies to avoid relying on transitive dependencies.

[Sbragul26]

Can you please check and update this?

Babel packages are using different versions. (Latest version is 8.0.0.)
Can you align all Babel packages to the same version to avoid any compatibility issues?

[KatalKavya96]

@Sbragul26 I tried moving the Babel packages to 8.0.0, but the checks started failing because the current setup still depends on Babel 7 tooling. @babel/preset-env requires Babel ^7.0.0-0, while Babel 8 was being loaded.

So I will keep the Babel packages aligned within the Babel 7 range for this PR. Moving to Babel 8 would need a broader migration separately.