d2933cc184
* build(ts): add ts webpack dependencies and config * wip(webpack.dev): css and js compiling * wip(webpack): building assets with watch * fix(webpack): fix page reloads not serving assets * build(webpack): fork typechecking * chore(webpack): rename dev config * build(webpack): add production config * build(webpack): add process vendor in separate build * build(webpack): change dev source map * build(webpack): dont lint in prod builds * build(webpack): move reduce redundancy for GIT_SHA * docs(ui): update README * build(webpack): add hash to production build |
||
|---|---|---|
| .. | ||
| assets | ||
| cypress | ||
| mocks | ||
| scripts | ||
| src | ||
| .browserslistrc | ||
| .eslintrc.js | ||
| .npmrc | ||
| .prettierrc.json | ||
| Makefile | ||
| README.md | ||
| cypress.json | ||
| index.d.ts | ||
| jestSetup.ts | ||
| package.json | ||
| testSetup.ts | ||
| tsconfig.json | ||
| webpack.common.ts | ||
| webpack.dev.ts | ||
| webpack.prod.ts | ||
| webpack.tsconfig.json | ||
| webpack.vendor.ts | ||
| yarn.lock | ||
README.md
Packages
Adding new packages
To add a new package, run
yarn add packageName
Adding devDependency
yarn add packageName --dev
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.
Starting Dev Server
The assets are built by running yarn start from withing the /ui directory. The dev server with hot reloading runs at localhost:8080.