Update package.json to use `npx`.

Also regenerated package-lock.json.

Change-Id: Ib0c41a8b17801d580b49c0203bb79eee63064f28
Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/2729405
Reviewed-by: Tiffany Zhang <zhangtiff@chromium.org>
Commit-Queue: Andrew Chang <andrewjc@google.com>
Cr-Commit-Position: refs/heads/master@{#38985}
GitOrigin-RevId: 7378414709b1e324d8bc6ecaa737be01a057dd94
15 files changed
tree: 49570fc8a116ec4bd8911ba3e120c4807c552776
  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 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.


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.