# Component Configuration File

Every component must have a configuration file. The configuration file defines the metadata values for the component, including supported targets and the design configuration for Lightning App Builder and Experience Builder.

The configuration file follows the naming convention `componentName.js-meta.xml`, such as `myComponent.js-meta.xml`.

Include the configuration file in your component’s project folder, and push it to your org along with the other component files.

Here’s the simplest configuration file.

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

For the complete list of elements in the configuration file, see [XML Configuration File Elements](/docs/platform/lwc/guide/reference-configuration-tags.md).

:::tip
If you don’t include a configuration file for your component, you get an error similar to the following when you push your changes.

```
Cannot find Lightning Component Bundle <component_name>
```
:::

**See Also**

- [Configure a Component for Lightning App Builder](/docs/platform/lwc/guide/use-config-for-app-builder.md)
- [Configure a Component for Experience Builder](/docs/platform/lwc/guide/use-config-for-community-builder.md)
- [XML Configuration File Elements](/docs/platform/lwc/guide/reference-configuration-tags.md)