-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement artifacts renderer - similar to Claude artifacts/v0 #32
Comments
Hello, a easy solution would be sandpack by codesandbox, |
@admineral yes! Would love a contribution if you have time 🙂 |
Nope sry |
I can do this. @bracesproul, do you want the same UI as in the above mentioned Reactor repo, or do you want to keep it simple without separate file tabs? |
We can also make use of this - https://github.com/e2b-dev/code-interpreter |
Another dependency … i dont think it runs locally …. Get your E2B API key Sign up to E2B here. |
@alchemistgo87 I would love a contribution! Let me do some more research into the proper API for this, and I'll update this GitHub issue body with a more detailed product spec. Then, if you're still up for implementing it I can assign this issue to you! |
hey @alchemistgo87 lets start with something simple and use the code sandbox API. I just updated the GitHub body with a more detailed spec, and if that all looks good to you, let me know and I'll assign this issue to you! |
Great, thanks for the update. I will start working on it today, you can assign me the issue. |
Sweet! Looking forward to it @alchemistgo87 |
hey @alchemistgo87 going to unassign you from this, if you've already started feel free to still put a PR up though! |
Feature: React Code Rendering in Chat Interface
Primary Objective:
Enable users to view and interact with generated React code both in raw form and as a rendered application.
Key Requirements:
ArtifactRenderer
sectionisStreaming
true):Rationale: Prevents partial or invalid renders during code generation
Rationale: Ensures users can continue viewing working code while addressing issues
The
ArtifactCodeV3
interface should be updated with a new fieldsandboxURL
so each revision can store the sandbox URL. This means when a user navigates between different revisions, it should update the rendered code.Finally, in the final PR, it would be great if you could include a cost analysis so I have a rough idea as to how much it will cost.
The text was updated successfully, but these errors were encountered: