Espen Hovlandsdal

Could you open an issue in https://github.com/sanity-io/code-input and ask there whether or not it would be accepted? The code and ownership of the module has now moved.

Closing this as #4143 has now landed, but will leave the branch around in case we might need it.

Note that [Sanity Studio v3](https://www.sanity.io/blog/sanity-studio-v3-simplified-yet-powerful-customization) is now released and should fully support pnpm!

In [Sanity Studio v3](https://www.sanity.io/blog/sanity-studio-v3-simplified-yet-powerful-customization), we're no longer relying on Webpack, and the schema loading is done through ESBuild - so this shouldn't be an issue there. We are unlikely to...

Would also love to be included! Testflight form filled.

> The problem with #70 is similar to the astro problem we [solved for in `@sanity/pkg-utils`](https://github.com/sanity-io/pkg-utils/pull/172) with [a related PR in `sanity`](https://github.com/sanity-io/sanity/pull/4798) Ah, makes sense. Thanks for the background!

You can implement renderers for specific marks (eg annotated text spans) using the `marks` prop, but not the very leaf nodes (pure text). Do you have a use case for...

Have you tried using [@portabletext/react-native](https://github.com/portabletext/react-native-portabletext)? It should use `Text` by default

Getting errors of `The CJS build of Vite's Node API is deprecated`. Not sure _quite_ how to resolve this - esbuild-register kind of messes up the stack trace, and the...

Having said that, if we can make it still make it work with today's solution, I'd be more than happy to look at the altered approach.