API Versioning

Beginning in Winter '24, LWC supports versioning for custom components. Beginning in Spring ’25, versioning is required for all custom components.

Components that were previously saved without setting an API version continue to run as before. However, the next time you modify the component, you'll need to set the API version, too. Attempting to save an unversioned component to Salesforce results in an error.

When a component specifies a version, the component then depends on that specific version of a Salesforce release. Every HTML, CSS, and JS file of a component corresponds to one API version. The API version tells the LWC framework to behave as it did for the Salesforce release corresponding to the specified API version for that component. This ensures a stable execution environment for your components.

See Also

• Version Lightning Web Components