Snorre Eskeland Brekke

@xanderjl hey, thanks for reporting! This is definitely a problem with the ace dependency: it interacts with the window object directly without any checks. This fails in a node environment,...

So much for me writing unit tests to reproduce when I didnt test it a SSR stack 🙈

I think you would have to make a fork. But from what you are saying, simply adding the hook to the preview comp should fix it right? I'll get on...

@xanderjl just released a [new version of code-input](https://github.com/sanity-io/code-input/releases/tag/v3.0.0-v3-studio.7) that also makes the ace-code async in the preview component. Let me know if it works out for you now; I just...

Thats great to hear! Thanks for testing it!

Some _unstable signal when work on this continues. These are the sanity/_unstable imports used by google-maps-input: DiffComponent, DiffComponentOptions, ObjectDiff, ArrayDiff, ObjectDiff, useUserColor, DiffTooltip, getAnnotationAtPath, DiffComponentResolver, ChangeIndicator

Awesome work! Sorry for the late response. An alternate approach to this, which does not require any code changes, is to put the components object in a memo, and capture...

We just added a "typing portable text" section to the README, let me know if it is helpful https://github.com/portabletext/react-portabletext#typing-portable-text

This should be fixed in [3.0.0](https://github.com/portabletext/react-portabletext/releases/tag/v3.0.0)