538ace0a48
Co-authored-by: Andrew Watkins <andrew.watkinz@gmail.com> Co-authored-by: Chris Henn <chris.henn@influxdata.com> |
||
|---|---|---|
| .. | ||
| assets/images | ||
| mocks | ||
| src | ||
| test | ||
| webpack | ||
| .babelrc | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .npmrc | ||
| README.md | ||
| jest.config.js | ||
| package.json | ||
| tsconfig.json | ||
| tslint.json | ||
| yarn.lock | ||
README.md
Packages
We are using yarn 0.19.1.
Run yarn run to see a list of available tasks.
Adding new packages
To add a new package, run
yarn add packageName
Adding devDependency
yarn add --dev packageName
Updating a package
First, run
yarn outdated
... to determine which packages may need upgrading.
We really should not upgrade all packages at once, but, one at a time and make darn sure to test.
To upgrade a single package named packageName:
yarn upgrade packageName
Testing
Tests can be run via command line with yarn test, from within the /ui directory. For more detailed reporting, use yarn test -- --reporters=verbose.