Graphtia documentation · reference
React, Next.js, WordPress and Laravel analysis
See how Explorer recognizes React / Next.js, WordPress, Laravel, which source relationships it exposes, and what remains outside static coverage.
These adapters add framework structure to the language index. The sections below separate detection, supported relationships, required source context and limits.
Explore an example: React · Next.js · WordPress · Laravel
React / Next.js
Trace component references, recognized hook use and static Next.js routes back to their source. Route-to-handler and navigation links require proven symbols and literal route information.
Which component does this JSX reference actually use?
Evidence to inspect- OrderPage to OrderSummary componentJSX reference
- OrderSummary component to Price componentJSX reference
- OrderSummary component to Imported useMemo hookrecognized hook use
Follow an exact JSX reference into its component, then inspect recognized child-component references and imported hook use. Matching a component name alone is insufficient.
Rendering, props flow and runtime mutation are not inferred. Component and hook relationships come from supported source identities; the diagram does not show rendering order.
Where is the handler behind this source-declared route?
Evidence to inspect- app/api/orders/route.ts to Declared /api/orders routeroute convention
- Declared /api/orders route to Exported GET handlerstatic handler binding
- Exported GET handler to HTTP provider declarationprovider evidence
Trace a supported App Router route file to its normalized route and exported handler. A configuration-only file remains navigable without becoming an HTTP provider.
Dynamic rewrites, arbitrary export wrappers, deployment and server-action transport remain outside this example. A route file and a proven exported handler supply the static provider declaration.
How it is recognized
A react or next dependency in a visible package.json; components additionally require accepted TS/JS symbols and JSX/class evidence.
Relationships you can inspect
JSX occurrence to the exact component selected by language facts; recognized imported React hooks.
App/Pages route declarations, exported App Router HTTP handlers and proven callable Pages API defaults; static next/link navigation.
Source-declared use client/use server roles.
Required source context
Indexed TS/JS/TSX/JSX source and package.json; handler exports and import identity must be present.
Coverage limits
Dynamic hrefs, rewrites, runtime routing, arbitrary wrapper exports, rendering/props dataflow and server-action transport are not inferred.
A route file with only configuration is not promoted to an HTTP provider; static execution roles do not prove deployment topology.
WordPress
Follow static hook and shortcode registrations to uniquely identified callbacks, and inspect REST declarations and asset references.
Which callback is registered for this hook?
Evidence to inspect- Plugin source to add_action registrationsource context
- add_action registration to Literal checkout_ready hookdeclares hook
- Literal checkout_ready hook to Exact record_checkout callbacksupported callback binding
Inspect a literal hook registration and follow it to a uniquely identified callback. Keep the plugin source context and callback evidence together while reviewing a hook change.
Hook execution order, conditional registrations, dynamic callbacks and database-registered behavior remain unresolved. A supported registration can identify a callback without running WordPress.
How it is recognized
Recognized Composer dependency, wp-includes/version.php with $wp_version, or a plugin/theme header plus a known WordPress API call.
Relationships you can inspect
add_action/add_filter registrations and exact callback bindings; do_action/apply_filters dispatch declarations.
add_shortcode bindings; register_rest_route HTTP providers; enqueue/register script/style asset references.
Plugin/theme headers as source-owned package context.
Required source context
Indexed PHP/HTML/CSS source; literal names and uniquely resolvable, qualified callback identity.
Coverage limits
Runtime hook order, conditional registration, DB-registered behavior and dynamic callback/REST options remain unresolved.
Namespace/import ambiguity and self/static/parent callbacks can leave a registration unbound.
Laravel
Inspect literal routes, controller bindings, middleware declarations, container registrations, model structure and Blade view references.
Which controller and middleware are declared for this route?
Evidence to inspect- Route declaration to GET /orders endpointdeclares route
- GET /orders endpoint to OrderController.indexhandler binding
- GET /orders endpoint to Declared auth middlewaremiddleware reference
Inspect a literal route declaration, its exact controller method and supported middleware references before changing an endpoint.
Macros, computed groups, contextual container behavior and effective authentication are not executed. Routes, handlers and middleware declarations can be inspected together as static source evidence.
How it is recognized
laravel/framework or illuminate/* Composer dependency, standard Artisan bootstrap, or an Illuminate Route-facade source witness.
Relationships you can inspect
Literal Route HTTP methods to route endpoints and exact class/method handlers.
Literal middleware dependencies and bind/singleton declarations tied to unique concrete classes.
Model/Authenticatable structure, ServiceProvider declarations and literal view() references to Blade documents.
Required source context
Indexed PHP and Blade source with Composer/project scope; exact namespace/import evidence for controller and container targets.
Coverage limits
Runtime macros/groups, contextual container resolution, dynamic middleware and computed views remain unresolved.
Eloquent runtime scopes/casts/events, Blade compilation and database state are not executed or inferred.
How to interpret a result
Inspect the source location, revision and relationship kind. A recognized registration is static evidence; it does not establish runtime behavior or compatibility with every framework release. Unresolved or ambiguous targets should remain part of your review.