Preview documentation changes for this PR: https://eui.elastic.co/pr_3715/

• We should probably do the same for es/test
• Instead of placing the new .d.ts in the top-level and requiring the project to add a configuration, it looks like we can put index.d.ts files in the lib/test&es/test dirs and typescript will automatically pick them up when importing that directory. This wouldn't allow imports from deeper directories, but we don't support that as a pattern from the lib/es directories either - i.e. everything has to start at the @elastic/eui entry.

put index.d.ts files in the lib/test&es/test dirs and typescript will automatically pick them up

Yep, this is a better approach. Tested in Kibana without altering tsconfig.

Preview documentation changes for this PR: https://eui.elastic.co/pr_3715/

The generated files don't look correct, all of the declare module statements define @elastic/eui/lib/test but that makes the index.ts definition re-export from the non-existent definitions

declare module '@elastic/eui/lib/test' {
	export { requiredProps } from '@elastic/eui/lib/test/required_props';
	export { takeMountedSnapshot } from '@elastic/eui/lib/test/take_mounted_snapshot';
	export { findTestSubject } from '@elastic/eui/lib/test/find_test_subject';
	export { startThrowingReactWarnings, stopThrowingReactWarnings, } from '@elastic/eui/lib/test/react_warnings';
	export { sleep } from '@elastic/eui/lib/test/sleep';

}

The generated files don't look correct

Good catch. Updated to include full module names.

Preview documentation changes for this PR: https://eui.elastic.co/pr_3715/

jenkins test this

"PUPPETEER_SKIP_CHROMIUM_DOWNLOAD"

Preview documentation changes for this PR: https://eui.elastic.co/pr_3715/