DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to render streamed OpenUI in a Vue, Svelte, or Angular app with Openui

Install the matching runtime to render OpenUI Lang output in a non-React front end.

Who it is forA front-end developer on Vue 3, Svelte 5, or Angular who wants model-driven UI without switching frameworks.

The problemMost of the built-in component libraries are React-based, so non-React teams need their own runtime to render streamed model output.

The outcomeA Vue, Svelte, or Angular app that defines model-renderable components and displays streamed OpenUI Lang as it arrives.

What you need first

  • Node.js with npm and npx, since the README install and scaffold commands use them
  • An LLM provider you can call from your backend, because OpenUI sends a generated system prompt to your model
  • A component library to use or define; the README provides built-in libraries in @openuidev/react-ui

Steps

  1. In your project folder, run npm install @openuidev/vue-lang for Vue, npm install @openuidev/svelte-lang for Svelte, or npm install @openuidev/angular-lang for Angular.
  2. Define the components the model may render using that framework's bindings.
  3. Generate the system prompt from that component library and send it with your model request.
  4. Render the streamed OpenUI Lang output in the matching view component.
  5. Send a test prompt and check that a component renders as the response arrives.

Prompt for your agent

Using the thesysdev/openui repo, install the matching runtime for the project at <target project path> (vue-lang, svelte-lang, or angular-lang) and render one streamed OpenUI Lang response. Expected output is a visible model-generated component; verify that it appears progressively rather than all at once.

Caveat. The README lists the Vue, Svelte, and Angular bindings without built-in component libraries, so you must define your own components for these frameworks.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page