commit | b43d6145432937d62c9a099a5114072f625495cd | [log] [tgz] |
---|---|---|
author | Tiffany Zhang <zhangtiff@chromium.org> | Tue Mar 02 20:15:59 2021 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Mar 02 20:16:42 2021 |
tree | 71c943cd331e03319b56d2668a192c367ad5d6a0 | |
parent | e366980fd0d660de81a5c2cc8b68bfbafe7d2e44 [diff] |
ChopsUI: Update docs to include non-Web Component code as well. Change-Id: I4d0b5ca624543b0b5a9faf409dde019d7c4ea4fe Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/2729604 Auto-Submit: Tiffany Zhang <zhangtiff@chromium.org> Reviewed-by: Dave Tu <dtu@chromium.org> Commit-Queue: Dave Tu <dtu@chromium.org> Cr-Commit-Position: refs/heads/master@{#38974} GitOrigin-RevId: f3b66201e21383c6593809e0692e2fe4188a7480
This directory contains Web Components and JavaScript libraries shared across Chrome Operations' application frontends.
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:
git clone
.npm run bootstrap
.npm test
.npm start
. The demos will be at http://localhost:8080/.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:
npm adduser
.To publish a new version:
origin/master
.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.npx lerna publish from-package
.