Salesforce Summer ’25 Release Updates For Developers

Salesforce Summer ’25 release is now live in the pre-release orgs, giving us an early glimpse into all the exciting new features coming our way. If you haven’t already, you can register for a pre-release org to explore everything firsthand here.

Going through the entire release notes can feel pretty overwhelming, but don’t worry, we’ve got you covered. In this blog, we’ll break down some of the key Salesforce Summer ’25 Release updates for developers that you should know about.

1. Use TypeScript with Lightning Base Components

TypeScript is a version of JavaScript that adds type checking and a bunch of other features to make your code stronger and easier to manage, especially in larger applications.

With the Summer ‘25 release, Salesforce has introduced type definitions for Lightning Base Components. This means developers can now import these definitions into their components for better type checking and handling.

import {LightningElement} from 'lwc';

import '@salesforce/lightning-types';

import type LightningButton from 'lightning/button';

export default class ComponentExample extends LightningElement {

submitLabel: string = 'Submit';

}

When you’re using a base component, you’ll need to import its type definition into your component. You can find these type definitions in the @salesforce/lightning-types package on npm.

2. Preview a Single Lightning Web Component Using Local Dev (Beta)

With the Salesforce Summer ’25 release, there’s a great new update for developers using Local Dev. If you’ve installed the local development plugin, you can now set up Local Dev to run a real-time preview of a single Lightning web component. Before this, you had to publish your component to an org first before you could even preview it with Local Dev.

Once you have Local Dev installed, just run the ‘sf lightning dev component’ command from the command line. In the CLI output, use your arrow keys to pick a component from the list of supported options.

After you select one, Local Dev will automatically open a new browser page showing a real-time preview of your component. It is important to note that for now, you can enable Local Dev for only sandbox and scratch orgs, and currently, this feature is in beta.

3. Dynamic Formulas in Template Mode

In the Summer ’25 release, Salesforce made an update to the FormulaBuilder class by adding a new method called parseAsTemplate(). This method lets you use merge field syntax to pull actual field values into your formula.

When you use parseAsTemplate(), the formula runs in what’s called “template mode.” That means instead of just returning a fixed value, it dynamically fills in the field values right into your formula string.

<p data-pm-slice="0 0 []">FormulaEval.FormulaInstance contactEmailFormula = Formula.builder()</p>
.withType(Schema.Contact.class)

.withReturnType(FormulaEval.FormulaReturnType.STRING)

.withFormula('{!name} ({!email})')

.parseAsTemplate(true)

.build();

In this example, we’re using parseAsTemplate set to true so that the formula works like a template. It replaces placeholders like name or email with the actual values from the Contact record when the formula runs.

4. SLDS Linter (Beta)

Salesforce has introduced the SLDS Linter to help developers bring their code in line with the latest Salesforce design system, SLDS 2. Whether you were working with HTML and CSS in Lightning Web Components or CSS and CMP files in Aura components, this tool made it easy to spot design issues.

It also gives you the ability to bulk-fix your code with just a single command, making cleanup and alignment with SLDS 2 much more efficient.

It is important to note that currently, SLDS Linter is in Beta.

5. Discover Your Apex Trigger Batch Size and User

You can now easily see your Apex platform event triggers configuration right in Setup, thanks to the new Batch Size and User columns. Before this update, you could only get that information through the Tooling API or the Metadata API using PlatformEventSubscriberConfig.

To check the trigger batch size and user for an Apex trigger, go to Setup, type “Platform Events” into the Quick Find box, click on Platform Events, and then select your platform event. On the event’s detail page, look at the Subscriptions related list — that’s where you’ll find the new info.

Also Read – Top Flow Features in Salesforce Summer ’25 Release

6. New Targets for Lightning Web Components

In the Summer ’25 release, Salesforce rolled out two new targets for Lightning Web Components to enhance agent actions.

lightning__AgentforceInput, allows developers to create components that receive input from users during agent actions and is perfect for configuring components that can accept input from a user.

lightning__AgentforceOutput, makes it possible to build components that display output from agent actions, helping agents display dynamic data right where they need it.

7. Reduced Timeout of Outbound Messages

Starting with the Salesforce Summer ‘25 release, the timeout for outbound messages has been reduced from 60 seconds to 20 seconds. With a shorter timeout, the system can use resources more efficiently and process more messages overall.

It also helps prevent long-running messages from holding up others that are waiting in the queue.

Also Read – Salesforce Summer ’25 Release Updates For Admins

Conclusion

We hope this overview of the Salesforce Summer ’25 release updates for developers helps you prepare for and make the most of the new features and enhancements. We’d love to know which updates you’re most excited about. Feel free to drop your thoughts and experiences in the comments!

Get a complete Roadmap To Learn Salesforce Admin and Development

Name *

First

Last

Email *

Comment or Message

Submit