---
schema_version: "1"
id: e8252f1715988a214b7359e754eda0698f31085844a23042c5ac911c34e32e5c
title: Get the Latest LWC Changes with LWC API Version 67.0
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/262-0-0/rn_lwc_versioning.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_lwc_versioning.htm&release=262.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7615e7334c9f8dcb45b7581af1594696de01147e23eecb17c94093a6525dde70
description: 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.
products:
  - Cross Cloud
release: "262"
---
# 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.

**How:** In the component's .js-meta.xml file, change the `<apiVersion>` value to 67.0.

```markup
<?xml version="1.0" encoding="UTF-8"?>
      <LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata">
      <apiVersion>67.0</apiVersion>
      </LightningComponentBundle>
```

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-release-notes-salesforce_release_notes-262-0-0-production-enus/e945111b-3e0a-4011-accc-d5949363bfcc/images/icon_important.png)

Important We recommend that upgrading your component API version one version at a time. For example, from 58.0, upgrade from 58.0 to 59.0, fix any errors or warnings you encounter, and then repeat until you get to the latest API version.

When a component’s LWC API version is set to 59.0 or later, it uses that value for its LWC framework version. Components that specify LWC API version 58.0 and earlier continue to work based on LWC framework behavior in Summer ’23 (API 58.0). When you set a component to use an earlier API version, you don’t get new features, bug fixes, and enhancements that are available only with later LWC API versions.

- **[Group Details Elements with the name Attribute](https://help.salesforce.com/s/articleView?id=release-notes.rn_lwc_versioning.htm&release=262.0.0&type=5)**  
    You can now add the `name` attribute to `<details>` elements in Lightning web components. Use the `name` attribute to create a group of `<details>` elements and keep only one element open at a time. Previously, using this attribute triggered a compiler warning.
- **[Improve Hot Module Reloading Performance](https://help.salesforce.com/s/articleView?id=release-notes.rn_lwc_versioning.htm&release=262.0.0&type=5)**  
    For faster code execution and better memory management, LWC API v67.0 improves hot module reloading performance.

#### See Also

- [_Lightning Web Components Developer Guide_: API Versioning](https://developer.salesforce.com/docs/platform/lwc/guide/get-started-api-versioning.html)

## Group Details Elements with the name Attribute

You can now add the `name` attribute to `<details>` elements in Lightning web components. Use the `name` attribute to create a group of `<details>` elements and keep only one element open at a time. Previously, using this attribute triggered a compiler warning.

**Where:** This change applies to Lightning web components in Lightning Experience, Experience Builder sites, and all versions of the mobile app in all editions.

**How:** Assign the same value to the `name` attribute on each `<details>` element that you want to group.

## Improve Hot Module Reloading Performance

For faster code execution and better memory management, LWC API v67.0 improves hot module reloading performance.

**Where:** This change applies to Lightning web components in Lightning Experience, Experience Builder sites, and all versions of the mobile app in all editions.