Prev Wong

When you use `` - you're creating/referencing a Craft Node, and Nodes are serialisable. We don't currently allow functions to be props of Nodes since we can't serialise functions. We...

Like what @matdru said, this error shouldn't have occurred in the first place, which suggests an underlying problem that we are not looking at. @tomgidden @flavienrako Does this issue this...

Can you try using yarn, and run `yarn build` at the root folder

Please create a minimal reproduction case of your issue on Codesandbox. Wrapping Craft's within an iframe should work.

Can't reproduce on my machine, might be OS related perhaps. @ankri @matdru Any ideas? 🤔

@matdru had a working prototype some time ago, would be great if we could get a PR on that! 🥰

The original intention was to have `data` and `children` to specify the initial editor state. I suppose we could have these props be reactive and trigger `deserialize` when they're updated....

Currently, we don't have a way to clear the history stack in the latest stable version of Craft. But if you're using the alpha `yarn install @craftjs/core@next` (which is version...

Hi @ITCuw, This is an expected behaviour for now. When you do this: ```tsx const YourComponent = () => { return ( ... ) ``` Essentially, that's creating a new...

I wonder how useful it is to know all the nodes that's currently being dragged over; or would it be more useful to just know which parent node is the...