Google Git
Sign in
chromium / infra / infra / crdx / chopsui-npm / refs/heads/main
commitbe078a8f00259e58faa8cbe24d11fa73d67c4f82[log] [tgz]
authorMostafa Draz <mdraz@google.com>Tue Apr 01 17:04:10 2025
committerCopybara-Service <copybara-worker@google.com>Tue Apr 01 17:04:53 2025
tree5a2a98cdae919ebb278d55cac546ad09d2cfe256
parent919dfc1dc8f9cfa7f703aaad757e6af0e6c01fba [diff]
luci: Remove unused package from lerna

Change-Id: I40390620d246b6e0578e76b451c1bae5d629546c
Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/6419984
Auto-Submit: Mostafa Draz <mdraz@google.com>
Commit-Queue: Tiffany Zhang <zhangtiff@chromium.org>
Reviewed-by: Tiffany Zhang <zhangtiff@chromium.org>
Cr-Commit-Position: refs/heads/main@{#72573}
NOKEYCHECK=True
GitOrigin-RevId: c3ee6cec98b962f2ab5eb600acb88a6014c20e59
1 file changed
tree: 5a2a98cdae919ebb278d55cac546ad09d2cfe256
  1. demos/
  2. elements/
  3. karma-reporter/
  4. test-helpers/
  5. trusted-types-policy/
  6. .eslintrc.cjs
  7. .gitignore
  8. index.html
  9. karma.conf.js
  10. lerna.json
  11. package-lock.json
  12. package.json
  13. README.md
  14. tsconfig.build.json
  15. tsconfig.json
  16. tslint.json
  17. webpack.config.js
README.md

chopsui

This directory contains Web Components and JavaScript libraries shared across Chrome Operations' application frontends.

Using chopsui components

Find the name of the specific component and install it within the @chopsui package scope. For example, to install chops-header, run npm install @chopsui/chops-header.

Contributing

To set up project development:

  1. Clone this repo with git clone.
  2. Install dependencies with npm run bootstrap.
  3. Run tests with npm test.
  4. Run demos with npm start. The demos will be at http://localhost:8080/.

Publishing packages

ChopsUI packages are published publicly on npm under the @chopsui organization.

Each component is published under a separate npm package. Packages are managed using Lerna. All packages are published together using a single version number kept in the lerna.json file under the version key.

To set up:

  1. Send your npm username to zhangtiff@ to be added to @chopsui.
  2. Authenticate in npm with npm adduser.

To publish a new version:

  1. Make sure your package has the following in package.json
    "publishConfig": {
  "access": "public"
}
  2. Sync a clean branch with upstream set to origin/main.
  3. Create a new version with npx lerna version --no-git-tag-version. Lerna will prompt you to select a new version number, detect which packages have changed since the last version, and locally update the json files.
  4. Commit the changes, upload them for code review, and land them.
  5. Sync to the newly landed commit.
  6. Publish to npm with npx lerna publish from-package --no-git-tag-version.