class

Analyzer::Javascript::Nextjs

Inherits Analyzer::Javascript::JavascriptEngine < Analyzer < FileHelper < Reference < Object

Constants

EXPORT_VERB_BRACE_RES = HTTP_METHODS.map do |m| {m, /export\s+\{[^}]*\b#{m}\b[^}]*\}/} end.to_h
EXPORT_VERB_CONST_ARROW_RES = HTTP_METHODS.map do |m| {m, /export\s+const\s+#{m}\s*=\s*(?:async\s*)?(?:\([^)]*\)|\w+)(?:\s*:\s*[^=]+?)?\s*=>/} end.to_h
EXPORT_VERB_CONST_BRACE_RES = HTTP_METHODS.map do |m| {m, /export\s+const\s+\{[^}]*\b#{m}\b[^}]*\}\s*=/} end.to_h

export const { POST } = serve<Input>(...) — handler(s) destructured from a factory call (e.g. @upstash/workflow/nextjs). The plain brace regex misses it because const sits between export and {.

EXPORT_VERB_CONST_RES = HTTP_METHODS.map do |m| {m, /export\s+const\s+#{m}\s*=/} end.to_h
EXPORT_VERB_FUNCTION_RES = HTTP_METHODS.map do |m| {m, /export\s+(?:async\s+)?function\s+#{m}\b/} end.to_h

Compiled once per verb — interpolated regex literals would otherwise be rebuilt (full PCRE2 compile) for every method on every file.

EXPORT_VERB_FUNCTION_SIG_RES = HTTP_METHODS.map do |m| {m, /export\s+(?:async\s+)?function\s+#{m}\b\s*\([^)]*\)/} end.to_h
EXTENSIONS = [".js", ".jsx", ".ts", ".tsx", ".mjs"]
HTTP_METHODS = ["GET", "POST", "PUT", "DELETE", "PATCH", "HEAD", "OPTIONS"]
SPLIT_TOP_LEVEL_COMMAS_RULES = Noir::TopLevelSplit::Rules.new(nest: ((Noir::TopLevelSplit::Nest::Paren | Noir::TopLevelSplit::Nest::Bracket) | Noir::TopLevelSplit::Nest::Brace) | Noir::TopLevelSplit::Nest::Angle, quotes: "", escape: Noir::TopLevelSplit::Escape::None, strip: false, empties: Noir::TopLevelSplit::Empties::Keep, per_kind: false, clamp: true)

Unlike every other JS/TS splitter this one has NO quote handling at all, counts < > as nesting, and neither strips nor drops empty parts — reproduced verbatim from the body it replaces.

The two callers explain the shape: exported_alias_for_method passes the inside of an export { a, b as c } clause and extract_server_action_params passes a TypeScript parameter list, so generics have to nest ({ params }: { params: Promise<{ id: string }> }) but neither input can contain a string literal. Both strip each part and skip the empties themselves.

Class methods

tech_name
Source

Instance methods

analyze
Source
tech

Instance-side view of the same declaration. The per-file rescues live on this base class, which has no way to name the analyzer that is running inside them, so a skipped file could not be attributed to a tech. Deriving it from analyzer_for keeps the name written exactly once.

Source