Incorrect type definition for PanelManager.addPanel

@artf - You didn't read the full sentence. You can clearly see in the code itself, it requires the argument given as the full Panel object. In your docs (as linked), you are not giving it the full Panel object in the example, but rather just an object with those projects. Your example is the following:

editor.Panels.addPanel({
  id: 'panel-top',
  el: '.panel__top',
});

Which TypeScript will complain about because the object given to it isn't an instance of a Panel nor is it an array of the object's properties.

The documentation on the site says the parameters given can be only an object with the properties

Sorry, where exactly do you read that statement?

Thanks for reporting this, @duclet.

The issue with Incorrect type definition for PanelManager.addPanel appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

1. Add a setTimeout wrapper to ensure the DOM has settled:

setTimeout(() => {
  // your operation here
}, 0);

2. Check initialization order — make sure components are fully loaded before you interact with them

3. Use the editor's event system — listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

• Test with the latest GrapesJS version if you haven't
• Provide a minimal reproducible example (CodeSandbox) — this helps the team identify the root cause faster
• Include GrapesJS version, browser, and console errors in your report