Salesforce Apex, LWC and Java Flow Analyzer › Guides › Map LWC to Apex
How to map LWC → Apex dependencies
A Lightning Web Component rarely stands alone — it imports Apex methods and nests child components. To understand or refactor one safely, you need to see those dependencies. Here's how to map LWC-to-Apex relationships visually, straight from your project folder.
Open Salesforce Apex, LWC and Java Flow Analyzer →Map the dependencies in 3 steps
- Open your project folder in Salesforce Apex, LWC and Java Flow Analyzer so both the LWC bundles and the Apex classes are indexed together.
- Read the architecture map. Each component's
@salesforce/apex/...imports become edges from the LWC to the Apex classes it calls, and LWC child components appear as their own linked nodes. - Drill in. Collapse nodes you don't need, expand ghost nodes for classes not yet loaded, and open any file's source to confirm exactly how it's wired.
What the map shows you
- LWC → Apex edges derived from real
@salesforce/apeximports — not guesswork. - Parent → child component structure, with LWC and LWC-child nodes color-coded distinctly.
- Apex, LWC, Java and HTML in one diagram, including cross-language links.
- Local & private — your bundle is read in the browser and never uploaded.
Before you change a shared Apex method, map it: you can immediately see which LWCs (and other Apex) call it, so nothing downstream breaks by surprise.
Frequently asked questions
- How do I see which Apex classes my LWC depends on?
- Load your project; Salesforce Apex, LWC and Java Flow Analyzer reads each component's
@salesforce/apeximports and draws an edge from the LWC to every Apex class it calls, visible directly in the architecture map. - Can I visualize LWC parent-child component structure?
- Yes — LWC components and their children appear as distinct color-coded nodes alongside Apex, Java and HTML, so you see both nesting and the Apex each component calls in one diagram.
- Does it work across Apex, LWC and Java at once?
- Yes. All three render together with cross-language links, so an LWC importing Apex (or Apex called by other Apex) shows up as connected nodes rather than separate views.