ckeditor5-react does not work with optimized imports

[stonebk]

📝 Provide detailed reproduction steps (if any)

Using optimized imports with @ckeditor/ckeditor5-react results in incompatible type errors in TypeScript.

I modified the Headless editor demo to include an optimized import to @ckeditor/ckeditor5-core and I get build errors.

/**
 * @license Copyright (c) 2003-2024, CKSource Holding sp. z o.o. All rights reserved.
 * For licensing, see LICENSE.md or https://ckeditor.com/legal/ckeditor-oss-license
 */

import React, { useState, useEffect, StrictMode } from 'react';
import { createRoot } from 'react-dom/client';
import { CKEditor } from '@ckeditor/ckeditor5-react';
import HeadlessEditor from './headless.js';
+import { EditorConfig } from '@ckeditor/ckeditor5-core/dist/index.js';

function App() {
	const [editor, setEditor] = useState(null);

+	const config: EditorConfig = {
+		placeholder: 'Type your text here!',
+	};

	return (
		<div className="App">
			<EditorToolbar editor={editor} />

			<CKEditor
+				config={config}
				editor={HeadlessEditor}

✔️ Expected result

No build errors.

❌ Actual result

❓ Possible solution

Switching the import from '@ckeditor/ckeditor5-core/dist/index.js' to '@ckeditor/ckeditor5-core/src/index.js' seems to resolve the build time error, but this required all imports to now point to src instead of dist, and this resulted in runtime errors:

This is actually the point I started from. I was previously using optimized imports before trying to upgrade with new installation methods when I ran into #17504. Upgrading without using the new installation method resulted in the same runtime error as above. I noticed that I was importing from src instead of dist so I tried updating all the imports and instead ran into the TS build error.

---

If you'd like to see this fixed sooner, add a 👍 reaction to this post.

[Witoso]

@amitjangid12 those issues are off-topic to this thread, please contact our support, as it relates to a premium plugin of our partner.

[Witoso]

@stonebk we will take a look at this with @filipsobol. Looks like our legacy support uncovered additional thing. We will figure this out, possibly we only need to maintain one set of types (src?) as the source generating this for src and dist is the same. Stay tuned.

[filipsobol]

Fixed in #17597