Forked native components break editor layout

Developer corner
,
1

Hi WeWeb team,

I’m experiencing a critical bug with forked native components in the WeWeb editor.

THE ISSUE
When I fork a native component (in my case, the AG Grid Datagrid), the forked version causes layout breaks in the editor, while the original native component works perfectly.

STEPS TO REPRODUCE

  1. Fork the native Datagrid component
  2. Add the forked component to a page in the editor
  3. Delete the forked component OR close a popup containing it
  4. Result: Editor layout breaks/explodes (requires page reload to fix)

KEY OBSERVATIONS

  • Bug only occurs in EDITOR mode (not in staging or production)
  • Bug happens even with ZERO code modifications after forking
  • Native component (non-forked) works fine - no layout issues
  • Seems related to component destruction/unmounting in the editor

WORKAROUNDS TESTED
I’ve tried several fixes:

  • Added onBeforeUnmount cleanup → didn’t help
  • Added editor mode guards → didn’t help
  • Reverted all code changes → bug still persists

This confirms the issue is with WeWeb’s fork system, not the component code itself.

ENVIRONMENT

  • Browser: Chrome (macOS)
  • Component: AG Grid Datagrid (likely affects all complex native components)

IMPACT
This prevents customizing native components through forking, which significantly limits extensibility.

An image in attachment to show the before after

Sans titre 2
Sans titre 21920×1362 132 KB

Sans titre
Sans titre2996×1806 246 KB

Thanks!
Florian

2

Hi @Florian :waving_hand:

Thanks for flagging this! Unfortunately, the community won’t be able to help you with this one.

The best way to report a bug that’s blocking your building is to create a bug ticket here and select the appropriate “Criticality”:

CleanShot 2025-12-02 at 10.46.04@2x
CleanShot 2025-12-02 at 10.46.04@2x1780×900 44.8 KB

UPDATE: I just checked in with the team and we have an open ticket to fix this issue. At this stage however, we don’t have an ETA for the fix because it’s a larger issue with the forking feature that requires deeper investigation.

PROPOSED WORKAROUND: In the meantime, one trick that seems to be working well is to use Cursor to create the coded component and import it into WeWeb. Here’s a tutorial on how to do that in case you’re interested: https://youtu.be/1A8wdH5Sb0o

3

Thank you kindly for your answer. I will dive into Cursor, but the Datagrid is already very interesting as it is, so I don’t really want to mimic it.
Cheers
F

4

Hey Florian, yeah, I completely understand.

Maybe you could fork our Datagrid here and use it as a starting point to ask Cursor or Claude code (https://youtu.be/s9HwpkSKONM?si=ih9XTddCjkT4qqRY) to improve it before you import it back?

5

so you mean that the fork is not working but the import seems to be a workaround ? I will try that
Thanks

6

Yes, exactly :slight_smile: We have an issue with the fork feature inside the editor at the moment, but you should still be able to import coded components from GitHub.