-
Notifications
You must be signed in to change notification settings - Fork 318
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
Idea for docs: Add support for playground persistence #832
Comments
This is 100% already planned! First we want to add support for multiple file tabs. This work is already underway. Once that is done, I would like to find a way to make the playgrounds shareable. Will have to experiment and decide if the URL state works well for this or not. URL state would be the preferred solution here. |
@orta That's what I want to do too! Btw, any help adding typescript type-checking support to the playground? We're using web containers (the thing that powers StackBlitz) and are willing to change the code editor being used. |
I've never used CodeMirror, but I'd look at https://github.com/val-town/codemirror-ts and then add the contents of the site's node_modules for react + stylex (and the |
Describe the feature request
Lately, I've been using Claude to prototype a UI, then convert it to StyleX afterward. This works surprisingly well, but I'd love to not rely exclusively on Claude. ChatGPT doesn't support something like artifacts for rendering UI yet.
That said, the new playground opens up the possibility to quickly generate code using any LLM based on the source code provided in the playground and quickly paste the results. This turns out to work!
What I'm hoping for now is simply the possibility for persistence in the playground tool.
Some ideas:
This was basically one shot by Claude once it understood it should use StyleX as opposed to Tailwind. I'd really like to be able to persist playgrounds such as this so I can scaffold dozens of ideas and bookmark them or share them for example on social media.
View Code Example
The text was updated successfully, but these errors were encountered: