What it is

Vike is a TypeScript, MIT-licensed full-stack web framework distributed through npm, and it lives in the JavaScript and Vite ecosystem. It is developed in a monorepo that produces the vike package and the create-vike-core scaffolding package, while the project documentation itself is published from the docs/ directory as the website vike.dev. The repository describes itself as a replacement for Next.js and Nuxt, and it is tagged with topics covering full-stack work on Node, server-side rendering, static site generation, and Vite plugin integration.

The concrete problem Vike addresses is the coupling that comes with an all-in-one meta-framework. Its tagline positions the project around building mission-critical applications with stability and development freedom, which is a direct response to the release cadence and opinionated conventions that application teams inherit when they adopt the paid-alternative-style frameworks it names. Rather than shipping a fixed set of runtime choices, Vike is structured as a core package plus framework-specific companions for React, Vue, and Solid, each of which exists as its own repository with its own extension packages for state and data fetching.

Key capabilities

• Server-side rendering for React, Vue, and Solid through the core package and the vike-react, vike-vue, and vike-solid companion packages.
• Static site generation, listed among the repository topics alongside server-rendering.
• Vite plugin integration, which makes Vike a plugin layer on top of the Vite build tool rather than a separate bundler.
• Full-stack application support on Node, as indicated by the full-stack and node topics.
• A scaffolding entry point in the create-vike-core package for starting new projects.
• Companion extension packages including vike-react-zustand, vike-react-query, vike-vue-pinia, vike-vue-query, and vike-solid-query.
• A maintained changelog file, CHANGELOG.md in packages/vike/, that records version history and breaking changes.

Who uses it and how

• Teams building React applications who want server rendering paired with Zustand or Query, using vike-react with vike-react-zustand and vike-react-query.
• Vue teams adopting the same rendering model through vike-vue, with Pinia and Query integrations available as separate packages.
• Solid developers who need server rendering via vike-solid and data fetching via vike-solid-query.
• Projects that prefer to layer rendering on top of an existing Vite setup instead of migrating the build toolchain.
• Application owners who track upgrade risk by reading CHANGELOG.md before moving between versions, and who reach out for help through the FAQ page at vike.dev.

Getting started

The README points to the vike and create-vike-core packages on npm,