Dyad0.19.0 Beta 1
Experimental Docker support and new community templates
Dyad v0.19.0 Beta 1 introduces experimental Docker support for safer code execution in sandboxed containers, along with updated Supabase Edge Function handling and 3 new community templates!
Highlights
Docker support (experimental)
Dyad now lets you run your apps in a Docker container, which essentially provides a sandbox and makes it safer to run code on your machine. To get started, you'll need to download and install Docker Desktop if you don't already have it. Then, go to Settings and set the Runtime Mode to Docker.
The rest of the Dyad development experience should feel the same. Docker support is experimental, so please report bugs and let us know what can be improved.
Docker improves safety but isn't 100% secure. While containers isolate your code from your main system in a sandbox, malicious code could still potentially break out or cause harm. We recommend reviewing AI-generated code before running it.
Supabase Edge Functions do not verify JWT
Thanks @beaugast for highlighting that Supabase is now deprecating the verify JWT option for Supabase Edge Functions as part of their transition to JWT signing keys. Dyad's system prompt has been updated to instruct the AI to perform authorization checks in the Edge Functions.
If you edit an existing Edge Function through AI chat or manually in Dyad, Dyad will automatically deploy your updated Edge Function without verify JWT enabled. Please ensure your Edge Function has the proper authorization check.
3 new community templates
The Dyad community has added three new templates that you can start using today in the Hub page:
- Docker / Next.js / Lowdb / GHCR template by @stgreenb.
- Vue.js template by @k1lgor.
- Chrome extension starter template by @tonedice.
Thank you to all these community members for contributing their open-source templates! If you'd like to add your own template, check out this guide.
Other changes
This release improves Dyad's context management for JSON files, in particular:
- All JSON files are now included in the AI context so that configs and data files (e.g., translations) can be properly edited by the AI. If this uses up too many tokens in your context window, you can use exclude paths in manual context management.
- Full
package.jsoncontents are now sent to the AI to prevent issues where AI edits caused problems with npm scripts removal.
We have several contributions from our community members this release!
- Fix setup banner UI in chat page by @guaoo
- Fix text overflow for chat messages by @azizmejri1
- Use TypeScript in system prompt examples by @antont
Feedback
If you run into any issues or have suggestions for this release, the best way to share them is by reporting a bug and uploading a chat session.