https://github.com/genexuslabs/chameleon-controls-library
A library of white-label, highly-customizable and reusable web components.
https://github.com/genexuslabs/chameleon-controls-library
web-components web-components-library
Last synced: 4 months ago
JSON representation
A library of white-label, highly-customizable and reusable web components.
- Host: GitHub
- URL: https://github.com/genexuslabs/chameleon-controls-library
- Owner: genexuslabs
- License: apache-2.0
- Created: 2021-03-05T12:54:36.000Z (about 5 years ago)
- Default Branch: main
- Last Pushed: 2026-01-19T17:16:40.000Z (4 months ago)
- Last Synced: 2026-01-19T18:33:14.194Z (4 months ago)
- Topics: web-components, web-components-library
- Language: TypeScript
- Homepage:
- Size: 5.67 MB
- Stars: 4
- Watchers: 9
- Forks: 2
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
 [](https://app.netlify.com/sites/gx-chameleon/deploys) 
[](https://github.com/prettier/prettier)
# Chameleon
A library of white-label, highly-customizable and reusable web components.
Visit the [Chameleon Showcase](https://gx-chameleon.netlify.app) for general information, demos and documentation.
## Using this library
There are four strategies we recommend for using these web components.
### In frameworks (React, Angular, etc) using a design system like Mercury or Unanimo.
For this, we recommend consulting our repository [chameleon-integrations](https://github.com/genexuslabs/chameleon-integrations) that contains various examples demonstrating how to effectively use the Chameleon Controls Library in different frameworks and with different design systems.
#### React
- Run
```bash
npm i @genexus/chameleon-controls-library --save
```
- Starting with Chameleon version `6.4.0`, there is a CLI to create React Web Component wrappers. To create the wrappers, run the following command:
```bash
npx chameleon-generate-react
```
For example:
```bash
npx chameleon-generate-react ./src/chameleon-components
```
- **Tip**: We recommend adding this command to your `package.json` file before running the dev server and production builds, as it takes less than 300ms to execute.
For example:
```json
"dev": "npm run build.chameleon && ...",
"build": "npm run build.chameleon && ..."
"build.chameleon": "chameleon-generate-react "
```
If you are in a monorepo environment, you may need run the script with `npx chameleon-generate-react`, `yarn chameleon-generate-react`, etc.
- Finally, all you have to do is use the components in your project!
### In a Stencil project
- Run
```bash
npm i @genexus/chameleon-controls-library --save
```
- Add an import to the library inside `src/index.ts`:
```ts
import "@genexus/chameleon-controls-library";
```
- Then you can use the web components anywhere in your template, JSX, html etc.
### Node Modules
- Run
```bash
npm i @genexus/chameleon-controls-library --save
```
- Put a script tag similar to this `` in the head of your index.html
- Then you can use the web components anywhere in your template, JSX, html etc
### Script tag
- Put a script tag similar to this `` in the head of your index.html
- Then you can use the web components anywhere in your template, JSX, html etc
## Accessibility checker
Starting with Chameleon version `6.4.0` there is a new accessibility utility that checks if form elements have a valid label and notifies (`console.warn`) when they don't accomplish this condition. At this moment, it's supported in the following components:
- `ch-combo-box-render`
- `ch-edit`
- `ch-progress`
- `ch-slider`
The accessibility checker is enabled by default and can be disabled as follows:
```ts
import { disableAccessibilityReports } from "@genexus/chameleon-controls-library/dist/collection";
disableAccessibilityReports();
```
## Meaning of development status in each control
| Category | Description |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `"experimental"` | The control is in its early stages of the development. This phase is often useful for testing the control early, but it is very likely that the interface will change from the final version.
Breaking changes for the control can be applied in "patch" tags. |
| `"developer-preview"` | The control is in its final stages of the development. The interface and behaviors to implement the control are almost complete. The interface of the control should not change so much from the final version.
Breaking changes for the control can be applied in "patch" tags. |
| `"stable"` | The control's development is stable and can be safety used in production environments.
Breaking changes for the control can be applied in "major" tags. In some cases, two "major" tags would be used to deprecate a behavior in the control. |
## Local Development
```bash
npm i
npm start
```
### Running the tests
To run the unit tests for the custom elements, run:
```bash
npm test
```
To run the spec tests for a specific custom element, run:
```bash
npm run test.spec src/components/
## For example:
npm run test.spec src/components/layout-splitter/tests/fixAndUpdateLayoutModel.spec.ts
```
To watch changes for tests (spec and e2e), run:
```bash
npm run test.watch
```
To watch only one file, run:
```bash
npm run test.watch -- -- src/components/edit/.ts>
## For example:
npm run test.watch -- -- src/components/edit/tests/edit.e2e.ts
```
To watch only one folder, run:
```bash
npm run test.watch -- --
## For example:
npm run test.watch -- -- src/components/edit/tests/
```
### Building for production
To build the design for production, run:
```bash
npm run build
```