Local Dev is now called Live Preview. Single Component Live Preview and the Live Preview Visual Studio Code extension for Lightning web components are generally available. Use state managers to centralize and decouple data logic from component presentation. Review new and updated distortions in the Lightning Web Security Distortion Viewer. Preview and test features with Salesforce Release Manager, which is in beta. Update your Lightning Web Components API version to 67.0.
Note Looking for new and changed Lightning web
components, Aura components, and Aura component interfaces? See the lists of new and
changed items at the end of the Development section.
- Get the Latest LWC Changes with LWC API Version 67.0
Update the API version for your components to take advantage of new features and improvements. Versioning ensures that existing components aren’t affected when Salesforce ships new features, bug fixes, and performance improvements that change existing behavior. Versioning also helps Salesforce deprecate legacy features. - Local Dev is Now Live Preview
To better reflect the real-time nature of component, Experience site, and Lightning app previews, Local Dev is now called Live Preview. - Preview a Single Lightning Web Component in Your Browser (Generally Available)
Use Single Component Live Preview to run a real-time preview of a Lightning web component in your browser. This feature, which is now generally available, includes some changes since the beta release. - Preview a Single Lightning Web Component in Visual Studio Code (Generally Available)
To run a real-time preview of a Lightning web component directly inside Visual Studio Code (VS Code) or Code Builder, use the Live Preview VS Code extension. This extension is now generally available for Lightning web components. - Simplify Data Interactions with State Managers for LWC (Generally Available)
Group and manage data and its related logic more effectively within your apps with state managers. This feature, which is now generally available, includes some changes since the beta release. - API Distortion Changes in Lightning Web Security
Lightning Web Security (LWS) includes new security protections with more distortions for web APIs. ESLint rules matching the distortions are also available. - HTMLAnchorElement Distortion Blocks data: URI Scheme
The new distortion onHTMLAnchorElement.prototype.hrefblocks URLs that use thedata:URI scheme. Thedata:URI scheme can be used to create plain text download links, but that approach raises various security issues. Use theblob:URI scheme instead. - Preview Features with Salesforce Release Manager (Beta)
With Salesforce Release Manager, your organization can preview and test upcoming features in sandboxes by using the Development (Dev) channel. Salesforce Release Manager accelerates innovation, improves long-term quality, and provides you with greater control over feature consumption. Your feedback helps us improve the feature quality and shape the future of the product. - Load Large Lists Dynamically (Developer Preview)
Handle massive amounts of data without slowing down your web browser. Whether you’re showing 50 or 5,000 items, dynamic lists offer a smooth user experience by using virtualization to render items as you scroll. - Get Better Right-to-Left Support
Enjoy better right-to-left (RTL) support in Lightning Experience for orgs that use an RTL language like Arabic or Hebrew. Improvements include corrections to a wide range of layout, spacing, icon mirroring, border direction, and text alignment. - Improve Encapsulation in Base Components with Internal Method Changes
Salesforce is updating the internal implementation of several base Lightning components to use private methods. This effort aligns with modern web standards and doesn't impact the public API of the base components. - Aura Support in Lightning Out 2.0 (Generally Available)
Embed existing Aura components securely on external sites without loading the Aura runtime on the host page. Your components run in a sandboxed iframe with full security isolation, so host-page scripts can't access Salesforce session data. Aura interop is generally available for existing Lightning Out (Beta) customers who complete the Lightning Adoption Program (LAP) enablement process on a case-by-case basis. - Embed Lightning Out 2.0 Components Through Experience Cloud LWR Sites
Embed Lightning Out 2.0 components on external pages using Experience Cloud Lightning Web Runtime (LWR) sites. Lightning Out 2.0 now supports Experience Sites (CLWR) for both guest (unauthenticated) and registered (authenticated) user scenarios. Guest user access is available for the Build Your Own (LWR) and Lightning Out templates in Experience Cloud sites. Use an existing CLWR site or create a new one, associate it with your Lightning Out 2.0 app, and publish, then embed your components on any external page. - Convert Lightning Out (Beta) Host Pages to Lightning Out 2.0 Using the MCP Migration Tool (Pilot)
Convert your Lightning Out (Beta) host pages to Lightning Out 2.0 with less manual rewriting. The Model Context Protocol (MCP) migration tool in the Salesforce DX MCP server encodes differences between loaders,$Lightningcalls, and frontdoor-based authentication. AI-assisted clients connected to the Salesforce DX MCP server propose updated HTML and JavaScript. You still need administrator access for org configuration in Setup. - Control Partitioned SID Cookies for the Lightning Domain in Session Settings
Keep embedded Lightning experiences working as browsers limit third-party cookies. Cookies Having Independent Partitioned State (CHIPS) is a browser standard that isolates cookies per embedding site instead of blocking them outright, so each external site that embeds your Salesforce components maintains its own independent session. A new org preference applies CHIPS partitioning to the Lightning domain session ID so that cross-site embeds maintain valid sessions. Enable the preference in Session Settings to reduce session breakage for Lightning Out 2.0 and other Lightning-domain embeds. - Embed External Web Apps in Salesforce with Micro-Frontends (Developer Preview)
Embed existing React, Angular, Vue, or JavaScript web apps in Salesforce pages without rewriting them. Micro-Frontend (MFE) runs your web app in a secure, sandboxed iframe with built-in communication, and lets you deploy updates independently of Salesforce releases. - Exchange Data Between Salesforce and Embedded MFE Widgets (Developer Preview)
Give embedded widgets real-time access to record context and org data, and receive user-interaction events back, without custom integration code or managing authentication tokens. - Apply Brand Theming to Embedded MFE Widgets (Developer Preview)
Keep embedded widgets visually consistent with your brand. Propagate design tokens into sandboxed iframes using standard CSS custom properties without additional JavaScript wiring inside the widget. - Auto-Resize Embedded MFE Widgets to Fit Content (Developer Preview)
Embedded MFE widgets automatically resize their container to match content height. Dynamic forms, tables, and expandable sections render at their natural height without layout workarounds. - Protect Unsaved Changes in Embedded MFE Widgets (Developer Preview)
Prevent accidental data loss when users navigate away from a page with unsaved widget changes. The platform prompts users to confirm before discarding their work. - Navigate MFE Widgets with Keyboard and Screen Readers (Developer Preview)
Embedded MFE widgets support keyboard navigation and screen readers using standard browser controls. Users tab into and through widget content without additional host-side development. - Enforced Maximum Number of Actions in a Boxcar Request
The maximum number of Aura actions allowed within a single boxcar (XHR) request is 250. This limit was first announced in Summer ’23, but was not actively enforced. - Lightning Components Release Updates
Check out new release updates for Lightning components.