#convex chef internals

1 messages · Page 1 of 1 (latest)

dawn tartan
#

what does Convex's chef use for virtualization of the frontend?

pine pastureBOT
#

Hi @dawn tartan. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

I'm sorry, but the knowledge sources do not contain explicit information about what Convex's Chef uses for virtualization of the frontend. The available documentation describes Chef as an AI app builder that generates full-stack apps using Convex, Convex Auth, React, and Vite, but it does not mention any specific frontend virtualization technology or approach used internally by Chef. If you need more technical details about Chef's frontend virtualization, you may need to reach out to the Convex team directly or consult future updates to their documentationChef documentation.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@dawn tartan Kapa.ai is still learning and improving, please let me know how I did by reacting below.

rocky spade
#

Hey, Chef is based on Bolt which itself uses WebContainers to run Node.js processes inside of the browser

dawn tartan
#

hey, thanks for commenting. I meant to ask about the virtualization of the chat messages which I assume chef does? haven't tried it out. Support mentioned that you guys use react-window on the frontend

#

I'm trying to build a realtime chat app and using the react-virtuoso chat API because it fixes a lot of problems with rendering the messages properly but it only exposes an imperative API which is a bit annoying with Convex's reactive paradigm

rocky spade
#

We don’t use virtualization in Chef at the moment, but I spent some time ensuring that chat messages are memoized correctly