kibana/packages/kbn-ui-framework
Chandler Prall 3bad1fc328
Upgraded EUI to v29.3.0 (#78870)
* Upgraded EUI to v29.2.0

* Remove hacks on top of EuiHeaderLink(s)

* Actual update to eui@29.2.0

* Resolve typescript issue when omitting a key over a union

* Resolve nav menu test's expectations

* Fix lint issue

* Update to 29.3.0

* Revert vega snapshot update

I don’t think this was intended to change when I ran the updater

* [ui-shared-deps] strip proptypes from ui-shared-deps production build

Co-authored-by: cchaos <caroline.horn@elastic.co>
Co-authored-by: spalger <spalger@users.noreply.github.com>
2020-10-05 12:44:29 -06:00
..
components
dist Upgrade EUI to v17.0.0 (#52342) 2019-12-09 10:51:17 -06:00
doc_site move and unify postcss config into @kbn/optimizer (#73633) 2020-07-30 11:16:49 -07:00
generator-kui apply prettier styles 2020-05-22 09:08:58 +02:00
src [Lens] Filters aggregation (#75635) 2020-09-10 21:16:07 +02:00
Gruntfile.js move and unify postcss config into @kbn/optimizer (#73633) 2020-07-30 11:16:49 -07:00
package.json Upgraded EUI to v29.3.0 (#78870) 2020-10-05 12:44:29 -06:00
README.md Update readme for KUI to note deprecation (#34389) 2019-04-02 14:38:45 -07:00
yarn.lock Add lockfile symlinks (#55440) 2020-01-27 11:38:20 -05:00

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.