๐Ÿ“ฆ Kong / kongponents

๐Ÿฆ Kong Vue Component Library

โ˜… 160 stars โ‘‚ 26 forks ๐Ÿ‘ 160 watching โš–๏ธ Apache License 2.0
component-libraryvue
๐Ÿ“ฅ Clone https://github.com/Kong/kongponents.git
HTTPS git clone https://github.com/Kong/kongponents.git
SSH git clone git@github.com:Kong/kongponents.git
CLI gh repo clone Kong/kongponents
semantic-release-bot semantic-release-bot chore(release): 9.49.7 [skip ci] 0184c85 3 days ago ๐Ÿ“ History
๐Ÿ“‚ main View all commits โ†’
๐Ÿ“ .github
๐Ÿ“ .vscode
๐Ÿ“ cli
๐Ÿ“ cypress
๐Ÿ“ docs
๐Ÿ“ mocks
๐Ÿ“ nuxt
๐Ÿ“ sandbox
๐Ÿ“ src
๐Ÿ“„ .babelrc
๐Ÿ“„ .gitignore
๐Ÿ“„ .npmrc
๐Ÿ“„ .nvmrc
๐Ÿ“„ .stylelintrc.mjs
๐Ÿ“„ CHANGELOG.md
๐Ÿ“„ cypress.config.ts
๐Ÿ“„ eslint.config.mjs
๐Ÿ“„ index.html
๐Ÿ“„ lefthook.yaml
๐Ÿ“„ LICENSE
๐Ÿ“„ netlify.toml
๐Ÿ“„ package.json
๐Ÿ“„ pnpm-lock.yaml
๐Ÿ“„ postcss.config.cjs
๐Ÿ“„ README.md
๐Ÿ“„ renovate.json
๐Ÿ“„ SECURITY.md
๐Ÿ“„ tsconfig.json
๐Ÿ“„ vite.config.ts
๐Ÿ“„ README.md

Kongponents

Kong Kongponents

Publish Commitizen friendly Netlify Status

Kongponents is a Vue component library of frequently needed UI elements. They were developed to solve Kong's application needs, but are generic enough to use in any web application.

Documentation

Kongponents Docs are powered by VitePress and the source can be viewed here.

Committing Changes

This repo uses Conventional Commits.

Commitizen and Commitlint are used to help build and enforce commit messages.

It is highly recommended to use the following command in order to create your commits:

pnpm commit

This will trigger the Commitizen interactive prompt for building your commit message.

Enforcing Commit Format

Lefthook is used to manage Git Hooks within the repo. A commit-msg hook is automatically setup that enforces commit message stands with commitlint, see lefthook.yaml.

Approvals

  • All pull requests require review and approval from authorized team members.
  • Automated approvals through workflows are strictly prohibited.
  • There is an exception for automated pull request approvals originating from generated dependency updates that satisfy status checks and other requirements.
  • Protected branches require at least one approval from code owners.
  • All status checks must pass before a pull request may be merged.