component.json
Web component file
| Type | object |
|---|---|
| File match |
component.json
|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/component-json/latest.json |
| Source | https://www.schemastore.org/component.json |
Validate with Lintel
npx @lintel/lintel check
Properties
Indicates whether the component should be treated as private and not published to public registries.
The name of the component. Must be lowercase, can contain hyphens and underscores.
Type of the component (e.g., 'component', 'block', 'template').
URL to the component.
The repository location in the format 'username/repository'.
A brief description of the component's purpose and functionality.
The semantic version number of the component (e.g., '1.0.0').
Framework compatibility (e.g., 'react', 'vue', 'angular', 'svelte', 'alpinejs', 'laravel', 'web-components').
An array of keywords that describe the component, used for search and categorization.
The primary entry point file of the component.
Scripts that are part of the component. Can be specified as an array of files or an object with named entries.
Styles that are part of the component. Can be specified as an array of files or an object with named entries.
Json data that are part of the component. Can be specified as an array of files or an object with named entries.
Image assets that are part of the component. Can be specified as an array of files or an object with named entries.
Fonts that are part of the component. Can be specified as an array of files or an object with named entries.
Additional files that are part of the component. Can be specified as an array of files or an object with named entries.
Dependencies that are required by the component. Can be specified as an array of files or an object with named entries.
Local dependencies that are required by the component. Can be specified as an array of files or an object with named entries.
Remote dependencies that are required by the component. Can be specified as an array of files or an object with named entries.
Custom file paths configuration for the component.
Templates that can be imported to be used within the component.
Path to or URL of a demonstration of the component.
Development-specific configuration that extends the main configuration.
The license identifier under which the component is distributed (e.g., 'MIT', 'Apache-2.0').