@launchsecure/launch-kit 0.0.21 → 0.0.23

package/dist/server/graph/queries/classify.scm

@@ -39,3 +39,11 @@
   declaration: (function_declaration
     name: (identifier) @http_export_fn
     (#match? @http_export_fn "^(GET|POST|PUT|DELETE|PATCH|HEAD|OPTIONS)$")))
+
+; Detect Next.js Server Action directive: 'use server' at file top.
+; Tree-sitter represents the directive as an expression_statement whose only
+; child is a string literal — and it must be at program level.
+(program
+  (expression_statement
+    (string (string_fragment) @use_server_directive)
+    (#eq? @use_server_directive "use server")))

package/dist/server/graph/queries/db-calls.scm

@@ -1,3 +1,4 @@
+; ── Prisma / Drizzle shape ─────────────────────────────────────────────────
 ; db.user.findUnique(...), db.session.create(...), etc.
 ; Matches any <ident>.<model>.<method>() — no hardcoded DB identifier
 (call_expression
@@ -6,3 +7,23 @@
       object: (identifier) @db.identifier
       property: (property_identifier) @db.model)
     property: (property_identifier) @db.method))
+
+; ── Supabase shape ─────────────────────────────────────────────────────────
+; <client>.from("table").<select|insert|update|delete|upsert>(...)
+; Captures the table name string and the operation method. The "from_name"
+; capture must equal "from" — filtered at emit time.
+(call_expression
+  function: (member_expression
+    object: (call_expression
+      function: (member_expression
+        property: (property_identifier) @sb.from_name)
+      arguments: (arguments
+        (string (string_fragment) @sb.table)))
+    property: (property_identifier) @sb.method)
+  (#eq? @sb.from_name "from"))
+
+; Supabase but the `from()` call is on a function-call result, e.g.
+; getServiceClient().from("merchants").select(...)
+; The `object: (call_expression...)` above already covers this case because
+; tree-sitter's grammar allows any expression as `object` of a member_expression.
+; No extra pattern required.

package/dist/server/graph/queries/deep/jsx-semantic.scm

@@ -1,4 +1,4 @@
-; Self-closing JSX elements with props: <Input type="email" placeholder="..." />
+; Self-closing JSX with props: <Input type="email" placeholder="..." />
 (jsx_self_closing_element
   name: (identifier) @el.tag
   (jsx_attribute
@@ -6,7 +6,7 @@
     [(string (string_fragment) @el.prop.value.str)
      (jsx_expression (_) @el.prop.value.expr)])) @el.self
 
-; Opening JSX elements with props: <Button variant="destructive">
+; Opening JSX with props: <Button variant="destructive">
 (jsx_opening_element
   name: (identifier) @el.tag
   (jsx_attribute
@@ -14,6 +14,17 @@
     [(string (string_fragment) @el.prop.value.str)
      (jsx_expression (_) @el.prop.value.expr)])) @el.open
 
+; Self-closing JSX without props: <Shell />, <DuetLogo />
+; Captures the element so composition wrappers / providers / shells appear
+; in deep elements. The consumer keys by position, so this match coexists
+; with the prop-bearing pattern above when both apply.
+(jsx_self_closing_element
+  name: (identifier) @el.tag) @el.self
+
+; Opening JSX without props: <Shell>children</Shell>
+(jsx_opening_element
+  name: (identifier) @el.tag) @el.open
+
 ; JSX text content (direct text inside elements)
 (jsx_element
   (jsx_opening_element

package/dist/server/graph/queries/navigations.scm

@@ -20,44 +20,60 @@
   (#eq? @_router2 "router")
   (#match? @nav.method.template "^(push|replace)$"))
 
-; <Link href="..."> — scoped to Link elements only
+; <ANY href="LITERAL"> — opening element with href prop. Captures
+; <Link>, <a>, and any custom wrapper component (LinkRow, NavItem, …). The
+; resolver filters non-route literals out of the final edge set.
 (jsx_opening_element
-  name: (identifier) @_link_tag
+  name: (_) @nav.link.tag
   attribute: (jsx_attribute
     (property_identifier) @_href
     (string (string_fragment) @nav.link.literal))
-  (#eq? @_link_tag "Link")
   (#eq? @_href "href"))
 
-; <Link href="..."> — self-closing
+; <ANY href="LITERAL" /> — self-closing
 (jsx_self_closing_element
-  name: (identifier) @_link_tag2
+  name: (_) @nav.link.tag.self
   attribute: (jsx_attribute
     (property_identifier) @_href2
     (string (string_fragment) @nav.link.literal.self))
-  (#eq? @_link_tag2 "Link")
   (#eq? @_href2 "href"))
 
-; <Link href={`...`}> — template
+; <ANY href={`...`}> — template, opening
 (jsx_opening_element
-  name: (identifier) @_link_tag3
+  name: (_) @nav.link.tag.tpl
   attribute: (jsx_attribute
     (property_identifier) @_href3
     (jsx_expression
       (template_string) @nav.link.template))
-  (#eq? @_link_tag3 "Link")
   (#eq? @_href3 "href"))
 
-; <Link href={`...`}> — template, self-closing
+; <ANY href={`...`} /> — template, self-closing
 (jsx_self_closing_element
-  name: (identifier) @_link_tag4
+  name: (_) @nav.link.tag.tpl.self
   attribute: (jsx_attribute
     (property_identifier) @_href4
     (jsx_expression
       (template_string) @nav.link.template.self))
-  (#eq? @_link_tag4 "Link")
   (#eq? @_href4 "href"))
 
+; redirect('/path')  /  redirect(`/path/${id}`) — bare call. Convention from
+; next/navigation; matches by name regardless of import path so wrappers
+; that re-export `redirect` still work. Filtering noise: callers like
+; redirect(url) (variable) are skipped because we only capture string args.
+(call_expression
+  function: (identifier) @_redirect_fn
+  arguments: (arguments
+    .
+    (string (string_fragment) @nav.redirect.literal))
+  (#eq? @_redirect_fn "redirect"))
+
+(call_expression
+  function: (identifier) @_redirect_fn_tpl
+  arguments: (arguments
+    .
+    (template_string) @nav.redirect.template)
+  (#eq? @_redirect_fn_tpl "redirect"))
+
 ; window.location.href = '...'
 (assignment_expression
   left: (member_expression