WebClient tutorials: Convert tutorials to use Vite instead of NextJS
- Linguagem predominante
- Rust
- Estrelas
- 18
- Forks
- 34
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
I think we should switch to using Vite instead of NextJS. Vite allows us not to worry about server-side rendering and the issues that come with that when using the web client SDK. This will allow for cleaner and more readable tutorial code.
Nevertheless, I think we should include a separate section (disclaimer) in the docs that, when using NextJS, one has to use dynamic imports (including an example), which should be clearly visible to anyone working with the web SDK.
One of our pioneers, Zoro, are using Vite for their frontend, and I must say that their web client code is by far more cleaner than our current tutorial code, since they can avoid the dynamic import restriction using Vite.
Guia de contribuição
Direção de pesquisa
Find the existing Next.js tutorial code in the repository, likely in a `web-client` or similar directory. Understand how the current examples work and the dynamic import pattern mentioned. Research Vite setup and create equivalent examples. The goal is to replace the tutorial code with Vite-based versions and add a clear Next.js disclaimer section to the documentation.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- javascript, next.js, react, typescript, vite
- Domínio
- documentation, frontend, web-dev
- Tipo de issue
- Refatoração
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Status de atividade
- Pouca atividade
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 55/100