Build grapesjs with npm

@Swindler36 That error is that it can not found eslint. Did you run npm install?

@longdoan7421 I fixed this error. Thanks. I want to ask two new questions about webpack and babel.

1. I can use webpack and babel separately. However. I could not integrate them. How can I do this?
2. How can I build grapesjs without test by using it's npm files? I want to only generate bundle files.

Thanks for reporting this, @fzerman.

The issue with Question: Build grapesjs with npm 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