No description
  • TypeScript 97%
  • JavaScript 3%
Find a file
James Talton bd3580c134 chore: fix package lock
Signed-off-by: James Talton <talton@gmail.com>
2025-06-04 15:01:04 -04:00
.github feat: make a pf5 version of the plugin example (#25) 2025-04-30 10:35:56 -04:00
.husky style: commitlint 2025-04-23 10:43:06 -04:00
examples/ui-plugin-example-pf5 chore: update dependencies across packages 2025-05-29 15:53:34 -04:00
packages chore: update dependencies across packages 2025-05-29 15:53:34 -04:00
.gitignore UI plugin example (#18) 2025-04-29 14:05:47 -04:00
.prettierignore initial version 2025-04-23 10:29:45 -04:00
.prettierrc.json initial version 2025-04-23 10:29:45 -04:00
commitlint.config.js style: commitlint 2025-04-23 10:43:06 -04:00
eslint.config.js initial version 2025-04-23 10:29:45 -04:00
LICENSE.md initial version 2025-04-23 10:29:45 -04:00
nx.json chore: update nx configuration and dependencies 2025-05-29 15:55:58 -04:00
package-lock.json chore: fix package lock 2025-06-04 15:01:04 -04:00
package.json chore: update dependencies in package.json 2025-06-04 15:00:08 -04:00
README.md feat: make a pf5 version of the plugin example (#25) 2025-04-30 10:35:56 -04:00
tsconfig.json initial version 2025-04-23 10:29:45 -04:00
vite.config.ts fix: vite-plugin-externalize-deps (#30) 2025-05-02 10:01:25 -04:00
vitest.setup.ts feat: ui-plugin-loader (#7) 2025-04-24 16:06:07 -04:00
vitest.workspace.json UI plugin example (#18) 2025-04-29 14:05:47 -04:00

Ansible UI Packages

Mono repo containing all the public NPM packages developed by the Red Hat Ansible UI team.

Packages are in the packages directory.

The root of the project is generic containing shared configurations, and uses npm workspaces to automate scripts across workspaces.

Getting Started

  1. Prerequisites

    • Node 20.x and up
    • NPM 8.x and up
  2. Clone Repository

    git clone git@github.com:ansible/ui-packages.git
    
  3. Install Package Dependencies

    npm ci
    
  4. Run tests

    npm test
    

Development

Packages

Packages are in the packages directory.

When working with NPM packages, the packages can only be used by other packages after they have been built.

We are using NX to manage the repo. NX supports having tasks depend on other tasks. Using this functionality, the test task and depends on the build task. The guarentees that the build happens before test which is important as the packages need to be built before they are used.

There is a top level watch that should be used to keep package builds up-to-date while working with them.

npm run watch

Examples

Examples are in the examples directory.

To run an example, change the the example directory and run npm start.

cd examples/ui-plugin-example-pf5
npm start

Conventions

All commit messages should have a conventional commits formatted commit. This allows nx to generate release notes and automatically increment the version and publish the packages.

Name Description
BREAKING CHANGE: Increments the MAJOR in Semantic Versioning
feat: Increments the MINOR in Semantic Versioning
fix: Increments the PATCH in Semantic Versioning
build: Build
chore: Chores
ci: CICD
docs: Docs
style: Styling
refactor: Refactoring
test: Tests
perf: Performance