Proposal: a phased approach to improving JavaScript/TypeScript flow detection

[javierzhao712-png]

Context

The project FAQ notes that JavaScript and Go flow detection still need improvement. JavaScript and TypeScript syntax can already be indexed, but reconstructing complete execution flows is harder because many relationships are dynamic or defined by framework conventions.

I would like to discuss a small and testable improvement before opening an issue or pull request.

Problem

Some common JavaScript and TypeScript patterns are difficult to represent as complete execution flows:

1. Functions can be passed as callbacks instead of being called directly.
2. Express routes register handlers and middleware through framework APIs.
3. Modules can use aliases, re-exports, and dynamic imports.
4. Frameworks such as React and Next.js define some entry points through conventions.

For example:

app.post(
  "/orders",
  checkLogin,
  checkStock,
  createOrder
);