Google Git
Sign in
chromium / infra / infra / crdx / chopsui-npm / 7144f8c5802d08b8ec39c1107e5ffb1ea6daa6bd
commit7144f8c5802d08b8ec39c1107e5ffb1ea6daa6bd[log] [tgz]
authorWeiwei Lin <weiweilin@google.com>Tue Aug 18 21:22:35 2020
committerAnthony Polito <apolito@google.com>Tue Aug 18 22:21:25 2020
tree77865c5d2991d6cbe38ab24d931e4724571fb4c6
parent254449dcf944643fd2fcbde0798b81f67b872f39 [diff]
Copybara Service Migration Initialization.

GitOrigin-RevId: fb879cf924091377573630f83de3d4094383b02d
1 file changed
tree: 77865c5d2991d6cbe38ab24d931e4724571fb4c6
  1. demos/
  2. elements/
  3. karma-reporter/
  4. test-helpers/
  5. .copybara
  6. .eslintrc.json
  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 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. 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.