Analyzer::Javascript::Astro

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 src/pages/rss.xml.js → GET /rss.xml (endpoint) src/pages/posts/[id].json.ts → /posts/{id}.json

Page files (.astro, .md, .mdx, .html) are HTML pages — always GET. Every script file under src/pages/ (.ts, .js, .mjs, .tsx, .jsx) is an endpoint, api/ or not, exporting 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.