[Meta] Expanded Platform support #7630
Description
Note
This issue was split out from #2760 to provide an updated plan for how we provide support for various platforms. Reference it for additional historical context.
At a high-level, the only must-have for EUI is to support Kibana (and other Elastic products).
However, it is also desirable to expand coverage to support certain platforms and environments, even if they are not directly needed by Kibana.
There are a couple of reasons for this:
- Prototyping - Many folks will use EUI to prototype new projects and concepts, in more modern tech stacks. It is important that we already have that support, so that we do not slow down their progress. We do not want to be a blocker.
- Onboarding - Many folks that are onboarding into the Kibana development stack will seek to pull EUI into a new project in order to explore the library.
In terms of expanding coverage, there are a few things we need to consider addressing:
- SSR support / Next.js - This is a challenge for anyone prototyping in Next.js, which many folks in the company do. In fact, we even provide a Next.js starter project, which has fallen woefully behind on support and updates.
- Replace and/or revive the Next.js starter project - Users need an easy way to spin up next EUI based project for prototyping. The Next.js starter project could be useful for that. However, we could also consider another form of starter project that lets folks quickly spin up a new project for prototyping. A create-react-app template would be a simple option.
- Vite / ESM-only bundler support - Folks commonly try to use bundlers like Vite and run into issues with EUI. We should support this.
Vite support
- EuiDataGrid: regeneratorRuntime is not defined #6616
- moment.location is not defined #6635
- Vite/Rollup/ESBuild cannot process the dynamic imports in
EuiIcon#5463 - ts(7016) error when trying to import icons #5305
- Flaws in ESM Build result in failure to build with Vite, Snowpack, etc. #3521