Custom react components gets wrapped inside a div
Yeah, that's expected from the demo perspective. You can play around with the code and find your solution but I'm closing this as it's not a core bug.
Read full answer below ↓Question
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
Arc v1.61.1
Reproducible demo link
https://codesandbox.io/s/grapesjs-react-components-n6sff
Describe the bug
@artf First of all thank you for this amazing library. I was trying to create custom react components within grapesjs and came across this sandbox link from one of the previously reported issues related to react integration. [https://codesandbox.io/s/grapesjs-react-components-n6sff]
I was able to make custom react components work after referring the sandbox, however there is one problem that still remains. Whenever a custom react component is dragged in to the canvas the component equivalent code gets wrapped inside a div which has all the gjs data attributes can class names. This extra wrapper div that gets added is kind of a roadblock towards my goal of building a custom dnd UI builder as the final output is going to have lot of extra divs in it. Is there any way to avoid this behaviour of a default div getting added as a wrapper ? Checked the documentation and couldn't find any option to achieve the same. Any help is appreciated.
Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (2)
Yeah, that's expected from the demo perspective. You can play around with the code and find your solution but I'm closing this as it's not a core bug.
Thanks for reporting this, @maneeshp97.
The issue with Custom react components gets wrapped inside a div 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:
- Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
// your operation here
}, 0);
-
Check initialization order — make sure components are fully loaded before you interact with them
-
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
Related Questions and Answers
Continue research with similar issue discussions.
Issue #5705
Component tools misalign when the editor is resized
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link https:/...
Issue #6269
Component model and view inits every time it's dragged over every component present in Canvas on which it can be dropped into
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Version 130.0.6723.59 (Official Bui...
Issue #4248
Block drag and drop interaction fails within vscode extension webview
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? VSCode (WebView within VSCode extension) R...
Issue #5280
Event handler on view not bound to the component
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Version 115.0.5790.114 Reproducible...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins →Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.
Browse premium plugins →Related tutorials
In-depth guides on the same topic.
Tutorial
GrapesJS vs Webflow vs Builder.io vs Puck: Which Visual Builder to Choose in 2026
A practitioner's 2026 comparison of GrapesJS, Webflow, Builder.io, and Puck — pricing, AI features, lock-in, and a one-line rule for picking the right one
Tutorial
Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live
We're shipping a set of discovery upgrades. New label filters, a proper compatibility switch for GrapesJS vs Studio, one-click and a smarter sort bar.
Tutorial
Why use grapesjs shadcn for your template builder
Skip months of editor plumbing and start with a fully working visual builder — polished UI included.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.