[chopsui] Bump versions to 0.2.0

For publishing added features to chops-signin in https://crrev.com/c/1706920

Change-Id: Ib247a33055056e10c1a9ba0a6ab133e908d0b735
Bug: monorail:5939
Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/1761089
Reviewed-by: Tiffany Zhang <zhangtiff@chromium.org>
Commit-Queue: Jeff Carpenter <jeffcarp@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#25180}
Cr-Mirrored-From: https://chromium.googlesource.com/infra/infra
Cr-Mirrored-Commit: a4d8f4864744611eed4fae49e9de0adbd3aafc99
17 files changed
tree: 62b4a117ad0e3d4776db771bba19c7d6013e0e66
  1. .eslintrc.json
  2. .gitignore
  3. README.md
  4. demos/
  5. elements/
  6. index.html
  7. karma-reporter/
  8. karma.conf.js
  9. lerna.json
  10. package-lock.json
  11. package.json
  12. test-helpers/
  13. tsconfig.build.json
  14. tsconfig.json
  15. tslint.json
  16. webpack.config.js


This directory contains Web Components 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.


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. Sync a clean branch with upstream set to origin/master.
  2. 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.
  3. Commit the changes, upload them for code review, and land them.
  4. Sync to the newly landed commit.
  5. Publish to npm with npx lerna publish from-package.