Svelte/SvelteKit parity beyond the initial renderer

Abierto
  • ¿Algo no está bien?
#678 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
react, typescript
Área
developer-experience

Línea de trabajo

Start by reading the existing Svelte and React package docs and comparing @openuidev/svelte-lang with @openuidev/react-lang; use examples/svelte-chat and examples/openui-chat to understand the example experience. The issue proposes several possible work areas but does not settle scope or define completion, so get maintainer direction before choosing a change.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

question

Summary

OpenUI already has initial Svelte support through @openuidev/svelte-lang and examples/svelte-chat, which appears to address the original Svelte renderer request in #302.

I would like to help improve the next layer of Svelte/SvelteKit parity with the React-first experience, but I want to align on scope before opening implementation PRs.

This is intended as a roadmap/discussion issue, not a request to merge one large cross-package change.

Existing related issues

  • #302 added/requested the initial Svelte renderer and SvelteKit example. This issue should not duplicate that work.
  • #498 tracks tool provider support for Vue, which looks like a similar parity concern for non-React runtimes.
  • #368 discusses DX for schema/system prompt generation across backends.
  • #549 notes that Vue/Svelte renderer tests already exist and can be used as references for React renderer tests.

Current state

From the current repo structure and docs:

  • @openuidev/svelte-lang exists.
  • examples/svelte-chat exists as a SvelteKit + AI SDK example.
  • The main CLI create flow is still documented as scaffolding a Next.js app.
  • React has a broader product surface through:
    • @openuidev/react-lang
    • @openuidev/react-headless
    • @openuidev/react-ui
    • examples/openui-chat
    • CLI scaffolding

Proposed contribution areas

I would like maintainer feedback on splitting this into small PRs:

  1. Svelte/SvelteKit parity matrix

    • Document what is supported today in Svelte/SvelteKit vs React.
    • Separate intentional React-only areas from gaps that should be closed.

  2. Svelte renderer/runtime parity audit

    • Compare @openuidev/react-lang Renderer behavior with @openuidev/svelte-lang.
    • Check advanced runtime concerns such as:
      • tool provider support
      • Query / Mutation execution
      • loading and error reporting
      • state hydration
      • parse callbacks
    • Close small gaps where maintainers agree they should be supported.

  3. SvelteKit example hardening

    • Make examples/svelte-chat a strong canonical SvelteKit reference.
    • Verify setup docs, environment variables, generated prompt flow, dev/build commands, and examples.
    • Add tests/checks only where they follow existing repo patterns.

  4. CLI SvelteKit scaffold

    • Add a create option such as openui create --framework sveltekit, if maintainers want the CLI to support framework selection.
    • Reuse examples/svelte-chat as the source template if that fits the current CLI architecture.

  5. Future discussion: Svelte headless/UI packages

    • Discuss separately whether @openuidev/svelte-headless or @openuidev/svelte-ui should exist.
    • I would not start with new packages unless maintainers want to expand the public package surface.

Non-goals for the first PRs

  • No large all-at-once parity PR.
  • No duplicate implementation of the initial Svelte renderer already covered by #302.
  • No new public Svelte UI package without maintainer approval.
  • No broad refactors of lang-core or React packages unless needed for an approved scope.
  • No attempt to copy React APIs 1:1 where SvelteKit conventions call for a different API.

Suggested first PR

If this direction is acceptable, I suggest starting with either:

  1. a small Svelte/SvelteKit parity matrix doc, or
  2. a focused audit/fix PR for @openuidev/svelte-lang renderer/runtime parity.

Questions for maintainers

  1. Is this next layer of Svelte/SvelteKit parity something the project wants to accept incrementally?
  2. Should the CLI grow a SvelteKit framework option, or should SvelteKit remain example-only for now?
  3. Should tool provider / Query / Mutation parity be handled for Svelte similarly to #498 for Vue?
  4. Are new package surfaces like svelte-headless / svelte-ui in scope, or should contributions stay limited to svelte-lang, examples, docs, and CLI?
  5. Which first PR would be most useful to review?
Lenguaje dominante
TypeScript
Estrellas
10k
Forks
698
Merge medio
1 d 6 h
PR fusionados (30 d)
148

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de thesysdev/openui

Todos los issues de thesysdev/openui

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.