weka/weka-ui-components

Última actividad de origen registrada: 31 de marzo de 2026 a las 06:52

Catálogo de SkillsMP actualizado: 5 de noviembre de 2026 a las 19:57

skills recopiladas: 2

Estrellas en GitHub: 1
Forks en GitHub: 2

Instalar con un asistente de IA

Copia este prompt en el asistente de IA que estés usando.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/weka/weka-ui-components.

README del repositorio

Archivo de origen del README: README.md

Leer el README original

Mostrar README completo

# WEKA UI Components This package contains React components that should be used while developing UI for WEKA applications. ## Development 1. Run `yarn install` to install the necessary dependencies. 2. Run `yarn link` to create a symlink between the package and your local environment. 3. Inside the parent repository, run `yarn link "@weka/weka-ui-components"` to link the package. 4. Run the parent repository with the `--force` option to see changes. ## Release To release a new version of the package: 1. Open a pull request to the `main` branch. 2. A new release will be created for each merged PR. ## Storybook https://weka.github.io/weka-ui-components ## Run storybook locally yarn run storybook ## Commits Naming We are using [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). Here are some examples: - `feat: commit message (ticket)` - Use this for commits that introduce a new feature to the codebase. - `fix: commit message (ticket)` - Use this for commits that fix a bug in the codebase. - `chore: commit message (ticket)` - Use this for commits related to routine tasks or maintenance chores in the codebase. ## Pull Requests Flow 1. Open a pull request to the `weka-ui-components`. 2. Inside parent repositories where you want to update the components, run `yarn add @weka.io/weka-ui-components@https://github.com/weka/weka-ui-components#<pr_branch_name>` with your PR branch name instead of `<pr_branch_name>`. 3. Open a PR for the parent repository. 4. After merging the components PR, inside parent repositories where you want to update the components, run `yarn add @weka.io/weka-ui-components@https://github.com/weka/weka-ui-components#<latest_tag>` with the tag instead of `<latest_tag>` . 5. Update PRs for parent repositories. ### Automatic consumer updates Consumers are listed in `.github/consumer-targets.json` (`repo`, `path` of the frontend project, optional `commit_prefix`, default `chore:`): `weka/gohome` (`frontend`, `observe/frontend`) and `weka/wekapp` (`build/packages/dashboard/files`, commit prefix `UI:`). - A `weka-ui-components` PR and a consumer PR that share a ticket (`WH-123` or `WEKAPP-123`, in the title or branch) are linked automatically: the consumer PR gets a commit pointing at the UIC PR head (`pr-preview-consumers.yml`), and after a release open consumer PRs with the release's tickets are bumped to the new version (`update-consumers.yml`). - A consumer PR notifies this repo through the reusable `notify-consumer-pr.yml` workflow. ### Shared frontend CI for consumers Consumers call reusable workflows from this repo instead of keeping their own copies: ```yaml jobs: lint: uses: weka/weka-ui-components/.github/workflows/frontend-lint.yml@main with: { working_directory: frontend, project_title: WekaHome } secrets: { WEKA_COMPONENTS_NPM_TOKEN: ${{ secrets.WEKA_COMPONENTS_NPM_TOKEN }} } ``` - `frontend-lint.yml` runs ESLint, Stylelint, TypeScript and Prettier checks on changed lines and posts reviewdog comments. Inputs: `working_directory`, `project_title`, `node_version`, `tsc_flags`, `full_tree_checks`, `import_extensions_check`. Its scripts ship in this package under `plugins/ci/` (see `plugins/ci/README.md` for the `yarn` scripts a consumer must define); shared configs are exported as `@weka/weka-ui-components/stylelint` and `@weka/weka-ui-components/eslint-diff`. - `notify-consumer-pr.yml` takes an optional `ticket_pattern` (default `(WH|WEKAPP)-[0-9]+`). This repo is public, so any repo can call these workflows; the caller's Actions policy only has to allow workflows from `weka/*`. ## Dark Mode ### `index.html` Add to the `head` element: ```html <style> /* optimization to remove flickering between reloads */ html { background: #f5f5f5; } html.dark-mode { background: #3d3d3d; } @media (prefers-color-scheme: dark) { html { background: #3d3d3d; } } html.light-mode { background: #f5f5f5; } </style> ``` Add above all other scripts inside the `body` element: ```html <script> // optimization to remove flickering between reloads const savedDarkMode = localStorage.getItem('isDarkMode') if (savedDarkMode) { if (savedDarkMode === 'true') { document.documentElement.classList.add('dark-mode') document.body.classList.add('dark-mode') } else if (savedDarkMode === 'false') { document.documentElement.classList.add('light-mode') document.body.classList.add('light-mode') } window.addEventListener('DOMContentLoaded', () => { document.documentElement.classList.remove('dark-mode') document.documentElement.classList.remove('light-mode') }) } </script> ``` ### Usage Wrap your app with `DarkModeProvider` and call `useDarkMode` for getting the current value.

Cargando el README del repositorio…

Skills en este repositorio

Desarrolladores de software

1 categorías ocupacionales · 100% clasificado

skill

ocupación

descripción

actualizado

migrate-component

Desarrolladores de software

Migrate a component from observe/frontend to weka-ui-components v2

Idioma del texto original: inglés

2026-03-31

new-v2-component

Desarrolladores de software

Scaffold a new v2 component with all required files (tsx, scss, test, stories, index)

Idioma del texto original: inglés

2026-03-31

Mostrando 2 de 2 skills recopiladas.