Development Server: Lightning, Visualforce, and Flows

Development Server: Lightning, Visualforce, and Flows

aer server renders your org’s user interface from the metadata in your source: Lightning Experience pages, Setup pages, Visualforce pages, Aura components, screen flows, Lightning Web Components, and UI Bundles. See Development Server for how to start the server.

Lightning frontend

/lightning renders the org from its own metadata at Lightning Experience URLs: the app launcher, each app’s tabs, list views, record pages, the home page, reports, and dashboards. Pages use the FlexiPages, page layouts, compact layouts, record types, and list views in your source, and record pages show each field’s API name beside its label.

  • Apps. The app launcher lists the org’s CustomApplications and tabs. An org that defines no applications gets the standard Sales, Service, Marketing CRM Classic, and Salesforce Chatter apps. A Console app renders workspace tabs and subtabs and docks its utility bar at the bottom of the page.
  • Record pages. A record page uses the Lightning record page assigned for the app, the running user’s profile, and the record type, then the page layout, then a generated two-column page. Detail sections, related lists, tabs, the highlights panel, the sales path, Chatter feeds and publisher, Today’s Tasks and Today’s Events, Potential Duplicates with its merge wizard, and component visibility rules render. A custom LWC, Aura component, or screen flow on the page runs, with a caption naming it. A component aer does not implement renders as a placeholder that names it and lists its properties.
  • Forms. New, edit, and clone forms follow the page’s Dynamic Forms field sections when it has them, and the page layout otherwise, with record type prompts, dependent picklists, State and Country picklists, polymorphic lookups, and + New <Object> in lookups. A save error appears under the field it names.
  • Actions. Edit, Delete, Clone, Change Owner, Change Record Type, Sharing Hierarchy, View Account Hierarchy, Send Email, Log a Call, lead Convert, Submit for Approval, custom buttons and links, global and object quick actions, flow, LWC, Visualforce, and Aura quick actions, and the Chatter Post, File, and Link actions run from the record page. Send Email sends the message as Messaging.sendEmail does, so it is delivered over SMTP only when the server was started with --allow-email.
  • Reports and dashboards. /lightning/o/Report/home browses report folders. A report renders as tabular, summary, matrix, or joined output with totals, editable filter values, and its chart. When Analytics.settings enables inline editing, detail rows can be edited in place, and the save runs triggers, validation rules, and flows. A dashboard runs each component’s report and renders bar, column, line, donut, and funnel charts, metric tiles, gauges, and tables. Every dashboard runs its reports as the user you are logged in as. With --use-dashboard-running-user, a SpecifiedUser dashboard’s reports run as the running user its metadata names, who must then exist in the server’s database.

Render reports

Record, home, tab, and dashboard pages, and the forms, end with a render report naming the page or layout that rendered, counting the components by outcome, and giving the render time. From it you can:

  • Open the page assignment screen (/lightning/r/<Object>/<Id>/pageassignment or /lightning/page/home/pageassignment), which lists every assignment that could name a page, in the order they are consulted, and says whether each was used, skipped and why, or never reached. It also names where the highlights panel’s key fields and the action buttons come from.
  • Check show to reveal the fields, components, and tabs that visibility rules hid, each labeled with the rule that hid it. The choice is remembered in the browser.
  • Choose another of the object’s Lightning record pages, labeled with the apps, profiles, record types, and form factors assigned to it, to view the record with that page.

Setup pages

/lightning/setup/SetupOneHome/home links to Setup pages that use Salesforce’s URL paths:

PagePurpose
Object ManagerObjects with their fields, record types, list views, validation rules, and triggers, each with a detail page
UsersThe org’s users
Apex ClassesEvery class with its source; run a test, debug a test, or execute a static method
Apex TriggersEvery trigger with its source
Anonymous ApexRun a block, with a debugger
Apex JobsAsync jobs with their status and errors; pause and resume the async worker, run a queued job, or debug it
Bulk Data Load JobsBulk API 1.0 and 2.0 jobs and their batches, with each batch’s request and response
Query EditorThe SOQL query runner, with an option to use the Tooling API
Record CountsObjects holding records, with their counts
Email TemplatesEvery email template with its bodies
Platform Events, Change Data Capture, Event ManagerThe org’s platform events and change events

Setup Home also lists the aer server options in effect, each with the flag that sets it. The password, session tokens, and certificate keys are never shown.

Visualforce

/apex/<PageName> renders a Visualforce page, running its controller and extensions, and /dev/visualforce lists the org’s pages. Forms submit and run the action their command button or apex:actionFunction names, the standard controller’s save, quicksave, cancel, edit, delete, and view actions run when the page’s controllers do not define them, and custom components render. Page blocks, input and output fields, links, images, panels, page messages, includes, and apex:slds render, and $Resource, $Label, URLFOR, and the branching functions are evaluated.

A page with renderAs="pdf", and PageReference.getContent() and getContentAsPDF(), produce a PDF through ufo, a separate program that implements the Flying Saucer renderer Salesforce uses. aer looks for it in AER_UFO_PATH, beside the aer executable, and on PATH.

Aura components

Aura components run in the browser wherever Salesforce shows one: on a FlexiPage, as a tab, in the utility bar, as a quick action or action override, at /lightning/cmp/c__<Name> for a component that implements lightning:isUrlAddressable, and at /c/<Name>.app for an application. The markup, controller, helper, and renderer run, with attribute binding, events, aura:method, $A.createComponent, and the lightning: and ui: base components. Packages carry their Aura bundles and Lightning web components, served under the package’s namespace.

Screen flows

/flow/<FlowApiName> runs a screen flow and /dev/flows lists the org’s flows. Screens render their inputs, choices, sections, display text, images, lookups, data tables, and the toggle, address, and message components, with visibility rules evaluated as you change values. An embedded LWC’s FlowAttributeChangeEvent values are stored in the flow’s variables. Each screen-to-screen segment runs as its own transaction, as in Salesforce.

Flow approval processes and orchestrations start when a record save meets their entry criteria. /dev/workitems lists the work items assigned to you: an interactive step’s work item runs the step’s screen flow, and an approval step offers Approve and Reject.

Local LWC preview

Open http://127.0.0.1:8080/dev/lwc in your browser to see a list of available Lightning Web Components. Click any component to render it in an isolated preview. The preview page injects mock @wire data and lets you interact with the component as if it were running in a Salesforce environment.

Combine --watch with LWC preview for a fast feedback loop:

  1. Start the server with --watch.
  2. Open a component preview in your browser.
  3. Edit the component’s HTML, JavaScript, or CSS.
  4. Save the file—the server reloads and the browser reflects changes.

LWC preview supports:

  • @api properties with editable inputs
  • @wire adapters backed by local Apex and schema
  • Component composition and slots
  • Lightning base components

UI Bundle preview

UI Bundles are listed at http://127.0.0.1:8080/dev/uibundle and served at their application URL, http://127.0.0.1:8080/app/c__<bundleName>, after you log in. The Data SDK shim resolves both @salesforce/platform-sdk and the older @salesforce/sdk-data import, and exposes the graphql.query and graphql.mutate API. Source-tree walkers skip node_modules and hidden directories.