class Analyzer::Javascript::Astro

• Analyzer::Javascript::Astro
• Analyzer::Javascript::JavascriptEngine
• Analyzer
• Reference
• Object

Overview

Astro is a filesystem-routed framework. Routes live under src/pages/ and the URL is derived from the file path:

src/pages/index.astro → GET / src/pages/about.astro → GET /about src/pages/users/index.astro → GET /users src/pages/users/[id].astro → GET /users/{id} src/pages/[...slug].astro → GET /{slug} (catch-all) src/pages/api/users.ts → exports drive verbs

Page files (.astro, .md, .mdx, .html) are HTML pages — always GET. API route files in src/pages/api/** (.ts, .js, .mjs, .tsx, .jsx) export named verb handlers (export async function GET(...), export const POST = ...). When no explicit verb export is found we fall back to the standard handler set (GET / POST / PUT / DELETE / PATCH) — same heuristic the Next.js analyzer uses for catch-all handlers.

Out of scope for this first cut:

• Astro endpoints under non-conventional src/pages/ roots (the path detection is hard-coded to /src/pages/).
• Per-handler request-helper scanning — Astro endpoints use standard Request (request.headers.get(...), request.json(), await request.formData()) but resolving reads accurately needs cross-call value tracking. Path placeholders still surface via the optimizer.

Defined in:

Constant Summary

API_EXTENSIONS = [".ts", ".js", ".mjs", ".tsx", ".jsx"]

EXTENSIONS = PAGE_EXTENSIONS + API_EXTENSIONS

FALLBACK_API_METHODS = ["GET", "POST", "PUT", "DELETE", "PATCH"]

Lowest-cost defaults for endpoints whose handler doesn't advertise its verbs explicitly. Mirrors the Next.js fallback.

HTTP_METHODS = ["GET", "POST", "PUT", "DELETE", "PATCH", "HEAD", "OPTIONS"]

PAGE_EXTENSIONS = [".astro", ".md", ".mdx", ".html"]

Instance Method Summary

• #analyze

Instance Method Detail