[Framework]: Vike

Name

Vike

Homepage

vike.dev

Install instructions

vike.dev/new => select "React" => scaffolds a Vike app that uses vike-react
npm create vike-core@latest => scaffolds a Vike app that uses a bespoke React integration

Is your framework open source?

Yes

Well maintained

• Bugs are quickly fixed
• Feature requests are triaged quickly (either put on the roadmap with prioritization, declined, or quickly implemented)
• CHANGELOG.md
• Vike team

Active community

• GitHub Discussions
• Discord

Clear onboarding

Scaffold new Vike app

Ecosystem compatibility

Vike provides unmatched flexibility regarding ecosystem integration, see Developer Experience section below.

Self-hosting option

All deployment strategies:

• Static host (using pre-rendering)
• Self-hosting
• Serverless/edge deployment (Cloudflare, Vercel, Netlify, ...)
• ISR (via vite-plugin-vercel)

Users can choose between zero-config integration (via Universal Deploy), or manual deployment/server integration (via renderPage()).

Developer Experience

Data fetching:

• Next-gen RPC via Telefunc (we're the authors of Telefunc)
  • React RFC #275: Stable useId() across Suspense for element-scoped caching
  • SvelteKit's RPC design was inspired by Telefunc
• As well as "old school" page-level data fetching via +data (which is sufficient for SSG).

All render modes:

• SSR
• Pre-rendering aka SSG. (First-class support, see +prerender.)
• SPA/MPA. (First-class support, e.g. client-only data fetching which is a common blocker with other frameworks.)

Polished details:

• Automatic frontend deployment synchronization
• Low-level i18n API, for full control over i18n
• Route Functions
• Route Guards
• Advanced Base URL support (Base URL for static assets != Base URL for the SSR server)
• URL rewriting
• User can seemlessly use hitory.pushState()
• Opt-in support for legacy browsers
• Zero-config interop, e.g. Tauri
• Infinite loop guards
• Errors & warnings meticulously crafted to be helpful
• React component stack injected into stack trace
• ...

Flexibility & Stability

Vike's main USPs are flexibility and stability.

By design:

• Vike is an agnostic core (and therefore stable), with low-level hooks that can support an unprecedented amount of stacks, tools, and new paradigms.
• Large suite of hooks.

By prioritization, for example:

• We treat blockers with high priority. (When users report they cannot achieve something, we care a ton to unblock them.)
• We enable users to access internals as temporary escape hatch.

[!NOTE]
Vike caters to companies that need extra flexibility and/or stability, see Vike use cases.

User Experience

Fast UIs:

• Progressive enhancement via HTML Streaming
• The developer has precise control over data lifecycle (e.g. +onCreateGlobalContext and +onCreatePageContext) for performance maximization.
• Prefetching
• Preloading
• Waterfall detection

Compatible with our future vision for React

Full support for React 19's HTML Streaming:

• Both Node.js and Web Streams
• Progressive Rendering
• Powered by react-streaming (for minimal boilerplate & config, making vike-react and vike-react-rsc a lot smaller and simpler)
• No known issues (both Vike's side and react-streaming's side)

Vite recently landed support for Server Components (@vitejs/plugin-rsc). Vike has experimental Server Components support via vike-react-rsc.

[!NOTE]
See also:

• Our design for progressive Server Components adoption
• React RFC #219: injectToStream (important for wide adoption of React 19's HTML Streaming)
• We were RSC early adopters

L’issue fournit des liens vers Vike et des détails d’onboarding, mais ne cite aucun fichier du dépôt, aucun test ni aucun emplacement concret dans la documentation. Commencez par comparer cette proposition à la structure existante de la documentation du framework et confirmez où de telles entrées doivent être placées. Le travail sera terminé lorsqu’un ajout convenu et relu décrivant Vike aura été accepté par les maintainers.