We've talked a lot about which projects & environments we want to support. I'm rolling those up into this ticket as a place to track discussions & decisions.

External (non-Elastic) targets mean we intend to support EUI running in those environments, Internal (Elastic managed) targets likely means we directly maintain & update as EUI releases.

Current targets

• EUI Gatsby starter (https://github.com/elastic/gatsby-eui-starter)
• codesandbox
• Create React App

Possibilities

• EUI Next.js starter (https://github.com/elastic/next-eui-starter)
• Server Side Rendering (Provide SSR support #2074)
• ESM-only systems such as snowpack and vite (Flaws in ESM Build result in failure to build with Vite, Snowpack, etc. #3521)

Acceptance criteria

Automated testing for projects and deployments that we expect EUI to support. Currently, we rely on manual build steps or testing suites (functional and/or unit tests) provided by consuming applications to check environment compatibility and catch instances of breaking API changes. Conversion to and adoption of TypeScript has helped at a low level, but we need broader, less manual means of understanding support coverage.

Outcome
A script or pattern of scripts that EUI engineers can run to:

1. Install EUI in various project target instances; [Meta] Environments/Projects we want to intentionally support #2760 tracks the discussion about which projects to support.
2. Run the consuming project's linting and / or testing suite(s).
3. Run a production build of the consuming project.
4. Detect and report failures and incompatibilities.