d73d73c0d4
I did this with a dumb editor macro, so some comments changed too. Also rename root package from platform to influxdb. In interest of minimizing risk, anyone importing the root package has now aliased it to "platform" so that no changes beyond imports were necessary in those files. Lastly, replace the old platform module to local path /dev/null so that nobody can accidentally reintroduce a platform dependency while migrating platform code to influxdb. |
||
|---|---|---|
| .. | ||
| assets/images | ||
| mocks | ||
| src | ||
| .browserslistrc | ||
| Makefile | ||
| README.md | ||
| index.d.ts | ||
| package-lock.json | ||
| package.json | ||
| testSetup.ts | ||
| tsconfig.json | ||
| tslint.json | ||
| yarn.lock | ||
README.md
Packages
Adding new packages
To add a new package, run
npm i packageName
Adding devDependency
npm i packageName -D
Updating a package
First, run
npm 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:
npm upgrade packageName
Testing
Tests can be run via command line with npm test, from within the /ui directory. For more detailed reporting, use yarn test -- --reporters=verbose.