Vike: a Next.js replacement spread across four repositories
(Replaces Next.js/Nuxt) 🔨 Build mission-critical applications with stability and development freedom.
At a glance
- What is it?
- Vike is the TypeScript framework its description offers in place of Next.js and Nuxt. What this repository actually holds is a 129 word README, a pnpm monorepo with three published outputs, nineteen example projects, and no framework binding of its own.
- Who is it for?
- Vike fits a team that wants the Next.js and Nuxt dependency replaced and accepts tracking four repositories plus a CHANGELOG.md inside packages/vike/ rather than one package with a pinned compatibility range. It does not fit anyone who needs the API surface or a framework binding from this repository alone, or who wants a 1.x line to depend on.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 3 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- vikejs/vike5,840 ★ · +9
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| vikejs/vike | 5.8k | 5.8k |
9 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
A 129 word README that is only an index
The README on main runs 129 words and holds no install command, no configuration example and no code sample. What it has is a four row link list: what Vike is at vike.dev, version history and breaking changes at packages/vike/CHANGELOG.md, a help page anchored on the FAQ, and a contribution guide at CONTRIBUTING.md. The pitch sits in the description in parentheses, a replacement for Next.js and Nuxt, with the stated goal being stability and development freedom. Everything else lives off this repository, on the documentation website.
Three source directories, three published outputs
The source to output table has exactly three rows. ./packages/vike/ produces the npm package vike. ./packages/create-vike-core/ produces create-vike-core. ./docs/ produces the website served at vike.dev. Nothing else at the top level publishes anything. The tree also holds packages/, examples/, skills/, test/, test-deprecated-design/, biome.json, vitest.config.ts, test-e2e.config.mjs, .npmrc, .ignore and .prettierrc, all of which are inputs to those three outputs rather than artifacts in their own right. The practical consequence for a reader is that the code which assembles a Vike app lives under packages/vike/ and not under examples/, and that the checks are driven from the repository root through vitest.config.ts plus test-e2e.config.mjs.
React, Vue and Solid support live in three other repositories
This is the constraint the README states most plainly and the one easiest to miss. The See also table sends every framework binding somewhere else. github.com/vikejs/vike-react publishes vike-react, vike-react-zustand, vike-react-query and further packages. github.com/vikejs/vike-vue publishes vike-vue, vike-vue-pinia and vike-vue-query. github.com/vikejs/vike-solid publishes vike-solid and vike-solid-query. A team that installs the vike package and then reaches for a UI library needs a second repository, at a version nothing in this tree pins. The examples/ list shows the same split: react-full, react-minimal, react-streaming, cloudflare-workers-react and cloudflare-workers-react-full sit beside vue-full, vue-minimal and cloudflare-workers-vue, with no Solid example at all. The description names Next.js and Nuxt as what Vike replaces, and this is the structural difference a replacement plan has to absorb, one package becoming four repositories to track.
First run on the pnpm workspace: install, dev, build, test
pnpm-lock.yaml and pnpm-workspace.yaml at the top of the tree settle the package manager question. The root package.json groups its scripts under comment keys such as ========= Dev, ========= Build and ========= Release, so the file reads as a checklist rather than a reference. For a first look, dev and build are the two that matter, and both delegate into packages/vike/ instead of running at the root.
pnpm install
pnpm run dev
pnpm run buildThe test entry point is the better measure of how much this repository checks, because it is three commands chained with &&, and the ecosystem variant adds one exclusion:
pnpm run test
pnpm run test:vite-ecosystem-ciThe second script exports VITE_ECOSYSTEM_CI=true and then runs vitest run, test-e2e --exclude test-deprecated-design and test-types. That exclusion is the most informative line in package.json. test-deprecated-design/ is still in the tree, so earlier designs remain readable, but they are kept out of the run that the external ecosystem job performs. Formatting and linting are pinned the same way, through a biome check --write --unsafe format script and a spellcheck script.
Nineteen example projects in examples/ carry the configuration answers
examples/ holds nineteen example projects plus its own README, and those directory names are the only catalogue of configuration surfaces in the repository. auth covers a login flow. base-url, base-url-cdn and base-url-server are three variants of one setting, which is a fair hint that the base URL is where the deployment differences live. render-modes is the only name that points at a Vike concept directly. custom-preload, html-fragments, i18n and path-aliases each isolate one behaviour. telefunc names RPC rather than rendering. file-structure-domain-driven names a layout convention, not a flag. Two of the three UI families ship both a minimal and a full form: react-minimal against react-full, and vue-minimal against vue-full. What a directory name cannot tell you is the value. No example file is quoted in the README, so every setting has to be opened in the repository itself.
v0.4.x releases and the CHANGELOG.md that owns the breaking changes
Three releases date the project precisely: v0.4.266 on 2026-09-02, v0.4.267 on 2026-09-28 and v0.4.268 on 2026-10-15. The last push to main was on 2026-11-02. The line is still 0.4.x, and the README's own link list points at /packages/vike/CHANGELOG.md under the label version history and breaking changes. That label is the warning that matters. There is no second major line to fall back to. The release scripts confirm that versioning happens inside the package rather than at the workspace root:
"release": "cd ./packages/vike/ && pnpm run release",
"release:minor": "cd ./packages/vike/ && pnpm run release:minor",
"release:major": "cd ./packages/vike/ && pnpm run release:major"release:commit sits next to them, so a version bump is part of the normal maintenance loop rather than an occasional chore.
llms.txt, skills/ and the API this repository does not carry
The last line of the README is an HTML comment addressed to agents, instructing them to load https://vike.dev/llms.txt and describing it as the Vike documentation index. The tree backs that up with a skills/ directory and with AGENTS.md and CLAUDE.md sitting beside CONTRIBUTING.md. The repository is deliberately built to be read by tools, which helps anyone automating setup or review. It is also the honest boundary of what is here. There is no configuration example, list of exported functions or page level API surface in the README. Read on its own, this tree tells you the layout, the release mechanics and the example catalogue, while the API itself has to come from vike.dev.
Editorial conclusion
Vike fits a team that wants the Next.js and Nuxt dependency replaced and accepts tracking four repositories plus a CHANGELOG.md inside packages/vike/ rather than one package with a pinned compatibility range. It does not fit anyone who needs the API surface or a framework binding from this repository alone, or who wants a 1.x line to depend on. Verify in this order: read packages/vike/CHANGELOG.md for the 0.4 range you would pin, open examples/render-modes and examples/base-url to see how the settings you actually need are written, and confirm the binding package version you plan to add sits inside that changelog range.
Frequently asked questions
What does Vike replace, and does this repository ship React support?
The repository description places Vike as a replacement for Next.js and Nuxt and points to vike.dev for the explanation. React support is not published from here: vike-react, vike-react-zustand and vike-react-query all come from the separate vikejs/vike-react repository, with vike-vue and vike-solid kept in two others.
How do I install Vike, and where do the packages come from?
The README gives no install command and sends readers to vike.dev instead. This monorepo publishes two npm packages, vike from packages/vike/ and create-vike-core from packages/create-vike-core/, and the repository itself is worked on with pnpm, as pnpm-lock.yaml and pnpm-workspace.yaml show.
Is the 0.4 version line worth depending on?
The line is 0.4.x: v0.4.266 shipped on 2026-09-02, v0.4.267 on 2026-09-28 and v0.4.268 on 2026-10-15, with the last push to main on 2026-11-02. Breaking changes are tracked in packages/vike/CHANGELOG.md, so that file is where a version pair has to be checked.
Can I run the Vike documentation website locally?
Yes. The root package.json has a docs script that changes into docs/ and runs pnpm run dev, plus docs:build for the production build and docs:test for the CI pass. The docs/ directory is the source for the site served at vike.dev.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/vikejs-vike)Star history chart for your README
[](https://hysenlabs.com/projects/vikejs-vike)Was this useful?