mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
Your window into the Elastic Stack
6d5c816fff
# Backport This will backport the following commits from `main` to `8.x`: - [[React@18] Env variable to use React@18 (#193113)](https://github.com/elastic/kibana/pull/193113) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Clint Andrew Hall","email":"clint.hall@elastic.co"},"sourceCommit":{"committedDate":"2024-12-09T12:55:14Z","message":"[React@18] Env variable to use React@18 (#193113)\n\nPart of\r\nhttps://github.com/elastic/kibana-team/issues/1016#issuecomment-2454845292\r\n\r\nOur plan for React@18 packages upgrade is to let kibana contributors now\r\nthat we're going to bump React packages couple weeks in advance. In\r\naddtion to the final PR with green tests and Kibana deployed, we want to\r\ngive simple instructions on how to run React@18 locally easilly:\r\n\r\nThis PR allows to quickly toggle between version of React locally\r\nwithout having to do anything beyond an environment variable.\r\n\r\n`REACT_18=true yarn bootstrap` will alias `react` and `react-dom` to v18\r\nin the build.\r\n\r\nI check that this works as expected when starting from: \r\n\r\n- local dev server `yarn start` \r\n- local ftr `node scripts/functional_tests_server.js`\r\n- local unit tests `REACT_18=true yarn test:jest ...`\r\n\r\nPlease note: \r\n- **This PR doesn't implement this switch for dist build, as I don't\r\nthink we need this for our purposes.**\r\n- The plan is that we remove this switch soon after we merge React@18\r\nupgrade to main.\r\n\r\nIn addition to the switch this PR mutes a very noisy warning from\r\nReact@18 about legacy root `Warning: ReactDOM.render is no longer\r\nsupported in React 18. Use createRoot instead. Until you switch to the\r\nnew API, your app will behave as if it's running React 17.`. This\r\nwarning is expected as after we upgrade to React@18 packages (Phase 1)\r\nwe will be in the process of migrating to the new createRoot API (Phase\r\n2). However, it is very noisy and we want to mute it for now.\r\n\r\n\r\nCo-authored-by: Anton Dosov <anton.dosov@elastic.co>","sha":"d0fde5f8e12709c08b5486359b98699637dba80d","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:SharedUX","backport:prev-minor","React@18"],"number":193113,"url":"https://github.com/elastic/kibana/pull/193113","mergeCommit":{"message":"[React@18] Env variable to use React@18 (#193113)\n\nPart of\r\nhttps://github.com/elastic/kibana-team/issues/1016#issuecomment-2454845292\r\n\r\nOur plan for React@18 packages upgrade is to let kibana contributors now\r\nthat we're going to bump React packages couple weeks in advance. In\r\naddtion to the final PR with green tests and Kibana deployed, we want to\r\ngive simple instructions on how to run React@18 locally easilly:\r\n\r\nThis PR allows to quickly toggle between version of React locally\r\nwithout having to do anything beyond an environment variable.\r\n\r\n`REACT_18=true yarn bootstrap` will alias `react` and `react-dom` to v18\r\nin the build.\r\n\r\nI check that this works as expected when starting from: \r\n\r\n- local dev server `yarn start` \r\n- local ftr `node scripts/functional_tests_server.js`\r\n- local unit tests `REACT_18=true yarn test:jest ...`\r\n\r\nPlease note: \r\n- **This PR doesn't implement this switch for dist build, as I don't\r\nthink we need this for our purposes.**\r\n- The plan is that we remove this switch soon after we merge React@18\r\nupgrade to main.\r\n\r\nIn addition to the switch this PR mutes a very noisy warning from\r\nReact@18 about legacy root `Warning: ReactDOM.render is no longer\r\nsupported in React 18. Use createRoot instead. Until you switch to the\r\nnew API, your app will behave as if it's running React 17.`. This\r\nwarning is expected as after we upgrade to React@18 packages (Phase 1)\r\nwe will be in the process of migrating to the new createRoot API (Phase\r\n2). However, it is very noisy and we want to mute it for now.\r\n\r\n\r\nCo-authored-by: Anton Dosov <anton.dosov@elastic.co>","sha":"d0fde5f8e12709c08b5486359b98699637dba80d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/193113","number":193113,"mergeCommit":{"message":"[React@18] Env variable to use React@18 (#193113)\n\nPart of\r\nhttps://github.com/elastic/kibana-team/issues/1016#issuecomment-2454845292\r\n\r\nOur plan for React@18 packages upgrade is to let kibana contributors now\r\nthat we're going to bump React packages couple weeks in advance. In\r\naddtion to the final PR with green tests and Kibana deployed, we want to\r\ngive simple instructions on how to run React@18 locally easilly:\r\n\r\nThis PR allows to quickly toggle between version of React locally\r\nwithout having to do anything beyond an environment variable.\r\n\r\n`REACT_18=true yarn bootstrap` will alias `react` and `react-dom` to v18\r\nin the build.\r\n\r\nI check that this works as expected when starting from: \r\n\r\n- local dev server `yarn start` \r\n- local ftr `node scripts/functional_tests_server.js`\r\n- local unit tests `REACT_18=true yarn test:jest ...`\r\n\r\nPlease note: \r\n- **This PR doesn't implement this switch for dist build, as I don't\r\nthink we need this for our purposes.**\r\n- The plan is that we remove this switch soon after we merge React@18\r\nupgrade to main.\r\n\r\nIn addition to the switch this PR mutes a very noisy warning from\r\nReact@18 about legacy root `Warning: ReactDOM.render is no longer\r\nsupported in React 18. Use createRoot instead. Until you switch to the\r\nnew API, your app will behave as if it's running React 17.`. This\r\nwarning is expected as after we upgrade to React@18 packages (Phase 1)\r\nwe will be in the process of migrating to the new createRoot API (Phase\r\n2). However, it is very noisy and we want to mute it for now.\r\n\r\n\r\nCo-authored-by: Anton Dosov <anton.dosov@elastic.co>","sha":"d0fde5f8e12709c08b5486359b98699637dba80d"}}]}] BACKPORT--> --------- Co-authored-by: Clint Andrew Hall <clint.hall@elastic.co> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|---|---|---|
| .buildkite | ||
| .devcontainer | ||
| .github | ||
| api_docs | ||
| config | ||
| dev_docs | ||
| docs | ||
| examples | ||
| kbn_pm | ||
| legacy_rfcs | ||
| licenses | ||
| oas_docs | ||
| packages | ||
| plugins | ||
| scripts | ||
| src | ||
| test | ||
| typings | ||
| x-pack | ||
| .backportrc.json | ||
| .bazelignore | ||
| .bazeliskversion | ||
| .bazelrc | ||
| .bazelrc.common | ||
| .bazelversion | ||
| .browserslistrc | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitattributes | ||
| .gitignore | ||
| .i18nrc.json | ||
| .node-version | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| .puppeteerrc | ||
| .stylelintignore | ||
| .stylelintrc | ||
| .telemetryrc.json | ||
| .yarnrc | ||
| BUILD.bazel | ||
| catalog-info.yaml | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| FAQ.md | ||
| fleet_packages.json | ||
| github_checks_reporter.json | ||
| kibana.d.ts | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| package.json | ||
| preinstall_check.js | ||
| README.md | ||
| renovate.json | ||
| RISK_MATRIX.mdx | ||
| run_fleet_setup_parallel.sh | ||
| SECURITY.md | ||
| sonar-project.properties | ||
| STYLEGUIDE.mdx | ||
| tsconfig.base.json | ||
| tsconfig.browser.json | ||
| tsconfig.browser_bazel.json | ||
| tsconfig.json | ||
| TYPESCRIPT.md | ||
| versions.json | ||
| WORKSPACE.bazel | ||
| yarn.lock | ||
Kibana
Kibana is your window into the Elastic Stack. Specifically, it's a browser-based analytics and search dashboard for Elasticsearch.
- Getting Started
- Documentation
- Version Compatibility with Elasticsearch
- Questions? Problems? Suggestions?
Getting Started
If you just want to try Kibana out, check out the Elastic Stack Getting Started Page to give it a whirl.
If you're interested in diving a bit deeper and getting a taste of Kibana's capabilities, head over to the Kibana Getting Started Page.
Using a Kibana Release
If you want to use a Kibana release in production, give it a test run, or just play around:
- Download the latest version on the Kibana Download Page.
- Learn more about Kibana's features and capabilities on the Kibana Product Page.
- We also offer a hosted version of Kibana on our Cloud Service.
Building and Running Kibana, and/or Contributing Code
You might want to build Kibana locally to contribute some code, test out the latest features, or try out an open PR:
- CONTRIBUTING.md will help you get Kibana up and running.
- If you would like to contribute code, please follow our STYLEGUIDE.mdx.
- For all other questions, check out the FAQ.md and wiki.
Documentation
Visit Elastic.co for the full Kibana documentation.
For information about building the documentation, see the README in elastic/docs.
Version Compatibility with Elasticsearch
Ideally, you should be running Elasticsearch and Kibana with matching version numbers. If your Elasticsearch has an older version number or a newer major number than Kibana, then Kibana will fail to run. If Elasticsearch has a newer minor or patch number than Kibana, then the Kibana Server will log a warning.
Note: The version numbers below are only examples, meant to illustrate the relationships between different types of version numbers.
| Situation | Example Kibana version | Example ES version | Outcome |
|---|---|---|---|
| Versions are the same. | 7.15.1 | 7.15.1 | 💚 OK |
| ES patch number is newer. | 7.15.0 | 7.15.1 | ⚠️ Logged warning |
| ES minor number is newer. | 7.14.2 | 7.15.0 | ⚠️ Logged warning |
| ES major number is newer. | 7.15.1 | 8.0.0 | 🚫 Fatal error |
| ES patch number is older. | 7.15.1 | 7.15.0 | ⚠️ Logged warning |
| ES minor number is older. | 7.15.1 | 7.14.2 | 🚫 Fatal error |
| ES major number is older. | 8.0.0 | 7.15.1 | 🚫 Fatal error |
Questions? Problems? Suggestions?
- If you've found a bug or want to request a feature, please create a GitHub Issue. Please check to make sure someone else hasn't already created an issue for the same topic.
- Need help using Kibana? Ask away on our Kibana Discuss Forum and a fellow community member or Elastic engineer will be glad to help you out.