class Analyzer::Javascript::Fresh

• Analyzer::Javascript::Fresh
• Analyzer::Javascript::JavascriptEngine
• Analyzer
• Reference
• Object

Overview

Fresh is Deno's filesystem-routed framework. Routes live under routes/ and the URL is derived from the directory layout:

routes/index.tsx → GET / routes/about.tsx → GET /about routes/users/index.tsx → GET /users routes/users/[id].tsx → GET /users/{id} routes/api/users.ts → handler-driven verbs routes/[...slug].tsx → GET /{slug}

Verb shape:

• Page files (.tsx / .jsx) with a export default component render HTML — emit GET.

• Resource files export a handler object whose keys are HTTP verbs:

  export const handler: Handlers = {
      GET(req, ctx) { ... },
      async POST(req, ctx) { ... },
      PUT: async (req) => { ... },
  };

  Each verb-shaped key (method shorthand or property assignment) registers a route.

• If handler is a single function (no object), Fresh dispatches every method to it — fall back to the standard handler set (GET / POST / PUT / DELETE / PATCH).

Underscore-prefixed files (_app.tsx, _layout.tsx, _404.tsx, _500.tsx, _middleware.ts) are framework plumbing — not user-facing routes — and skipped.

Out of scope for this first cut:

• Per-handler request-helper scanning. Fresh handlers receive (req, ctx) — accurate read tracking needs cross-call value flow. Path placeholders still surface via the optimizer.
• Route groups ((group) directories — same convention as SvelteKit). Add when fixtures show real-world usage.

Defined in:

Constant Summary

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

EXTENSIONS = PAGE_EXTENSIONS + API_EXTENSIONS

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

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

PAGE_EXTENSIONS = [".tsx", ".jsx"]

SKIPPED_LEAVES = ["_app", "_layout", "_404", "_500", "_middleware"]

Files that are framework plumbing rather than routes.

Instance Method Summary

• #analyze

Instance Method Detail