e5d8d49164
* chore(NA): script to check for multiple version of same dependency * chore(NA): remove multiple versions for the same dependency * chore(NA): hook single_version_dependencies script into the CI * chore(NA): remove grunt from the CI hook integration * chore(NA): update kbn pm dist * chore(NA): fix typechecking * chore(NA): update code to run under last extract-zip version * fix(NA): multiple versions of the same type dependency * move validation to bootstrap (#13) Co-authored-by: spalger <spalger@users.noreply.github.com> * chore(NA): todo to remove logic to validate single version deps once we move into a single package.json * chore(NA): remove verify dependency versions jenkins task * chore(NA): update kbn pm dist file * chore(NA): remove last mention to verify_dependency_versions.sh fom tasks.groovy Co-authored-by: Spencer <email@spalger.com> Co-authored-by: spalger <spalger@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| components | ||
| dist | ||
| doc_site | ||
| generator-kui | ||
| src | ||
| Gruntfile.js | ||
| package.json | ||
| README.md | ||
| yarn.lock | ||
Deprecation notice
This package is set for deprecation and is actively being removed from Kibana.
The Kibana UI framework is a collection of React elements and Sass styles used to build legacy layouts in Kibana. It was primarily used during the 5.x and 6.x versions and is replaced by the Elastic UI framework. Portions of Kibana still utilize this package and until it is fully removed you can still compile and view the documentation using the instructions below.
Compiling KUI and viewing the docs
Compile the CSS with ./node_modules/grunt/bin/grunt uiFramework:compileCss (OS X) or
.\node_modules\grunt\bin\grunt uiFramework:compileCss (Windows).
You can view interactive documentation by running yarn uiFramework:start and then visiting
http://localhost:8020/. This will also start watching the SCSS files, and will recompile the CSS
automatically for you when you make changes.
You can run node scripts/jest --watch to watch for changes and run the tests as you code.
You can run node scripts/jest --coverage to generate a code coverage report to see how
fully-tested the code is.
See the documentation in scripts/jest.js for more options.