mrkeyoor.comAsk

nuxt/nuxttested 24 Aug 2026commit 2f40158

nuxt review

Nuxt is worth evaluating for a Vue team that wants integrated routing, several rendering modes, and server code.

  • Build 28 s
  • Tests failed
32 sto install
  • 1,523 packages
Webevaluationupdated 26 Oct 2026
+20stars / 7d

Nuxt is a full-stack framework for Vue applications and websites. Its README lists server rendering, static generation, hybrid and edge rendering, automatic routing, data fetching, auto-imports, TypeScript support, and a server/ directory.

Verdict

Nuxt is worth evaluating for a Vue team that wants integrated routing, several rendering modes, and server code. In our August 24, 2026 run at commit 2f40158, dependency installation took 32 seconds and the framework build took 28 seconds. The test command stopped during preparation after 20 seconds, so this run provides no individual test results and does not establish that Nuxt is broken. Start with a representative application route and validate the intended modules and hosting setup before adopting it.

We ran it

Lab card: what happened when we ran nuxt
Lab card from our sandbox run
Screenshot of nuxt (nuxt.com)
nuxt.com
Install✓ · 32s1523 packages · 637 MB
Build✓ · 28s
Tests✗ · 20sran, no count parsed
Repo1930 files~111,588 lines of source · 6.6 MB · 28 CI workflows · tests dir

Answers from our run

Does nuxt build from source?

Dependencies installed in 32 seconds (1523 packages), and the build succeeded in 28 seconds. We cloned commit 2f40158 into a clean Debian container with 3 CPUs and no project-specific setup.

Do nuxt's tests pass?

No. The project's own test command exited unsuccessfully after 20 seconds, and its output did not expose an individual test count.

Who should not use nuxt?

Teams committed to a different component framework and unwilling to adopt Vue.

What are the alternatives to nuxt?

Next.js, SvelteKit. Nuxt is worth evaluating for a Vue team that wants integrated routing, several rendering modes, and server code.

Setup3/5Under the body rubric, the August 24, 2026 run at 2f40158 completed installation in 32 seconds and the repository build in 28 seconds; test preparation stopped after 20 seconds. Starter setup was not measured.
Docs3/5The supplied contribution guide gives concrete installation, preparation, testing, and linting commands. The full documentation was not inspected, so breadth and accuracy across topics remain unverified.
Community2/5The supplied release and issue extracts show contributor and maintainer participation. Adoption, support response times, and overall community health were not measured.
Maturity3/5The v4.5.2 release notes document patch maintenance. Our run used a development checkout identifying Nuxt as 5.0.0-0 and did not complete test preparation or assess production reliability.

Discussed on

  1. hnThe Future of Nuxt17 points
  2. hnNuxt.js – A minimal framework for server-rendered Vue.js applications6 points

Who it’s for

Vue teams that want routing, rendering, data fetching, and server code within one framework.
Developers who prefer automatic routing and imports over assembling those conventions themselves.
Framework contributors prepared to work with a pnpm workspace and a separate development preparation step.

Who it’s NOT for

Teams committed to a different component framework and unwilling to adopt Vue.
Developers who prefer to assemble routing and rendering themselves.
Teams requiring verified production performance, module compatibility, or security assurance from this review: our recorded run did not assess those properties.

Setup reality

In our recorded run on August 24, 2026, commit 2f401585b31beabcae3115a742fd31a0e64a0a57 completed dependency installation in 32 seconds and the framework repository build in 28 seconds. The dependency summary recorded 1,523 packages and 637 MB. These are repository setup measurements, not application performance results or proof of an installed CLI.

The test command exited with code 1 after 20 seconds during fixture preparation. Its log reported that nuxt prepare was killed with SIGABRT. The command chain stopped before Vitest, type tests, and typechecking; no individual test results were established. The cause of the abort remains unknown.

The recorded sandbox had 3 CPUs, 8 GB of memory, and image lab-node:22. The test log identifies Node.js v22.23.2. Nuxt's contribution guide specifies Corepack, pnpm install --frozen-lockfile, and pnpm dev:prepare. Creating a starter application is a separate workflow from building this framework checkout.

A Vue framework decision, with a bounded repository check

Nuxt brings routing, rendering, data fetching, and server code into a Vue project. That makes it worth evaluating when a team wants those pieces to follow one framework's conventions. Our recorded repository build succeeded, but the test command stopped during preparation. The distinction matters when deciding what this review can establish.

The Nuxt README lists server-side rendering, static generation, hybrid and edge rendering, automatic routing with code splitting and prefetching, auto-imports, and TypeScript with zero configuration. It also advertises 300+ modules. These are upstream capability claims; our run did not exercise each feature, verify the module count, or establish compatibility across hosting platforms.

What our August 24 run established

Our recorded run began at 2026-08-24T22:09:07.396Z on commit 2f401585b31beabcae3115a742fd31a0e64a0a57, dated August 24, 2026. It measured the framework repository, whose install output identified the local Nuxt package as 5.0.0-0. It was not a test of the Nuxt v4.5.2 release discussed in the issue reports below.

The sandbox configuration recorded 3 CPUs, 8 GB of memory, and image lab-node:22. The test log reports Node.js v22.23.2. The repository summary recorded 1,930 files, approximately 111,588 source lines, 6.6 MB before dependencies, 28 CI workflow files, a tests directory, workspaces, and no Dockerfile or Compose file.

Dependency installation completed successfully in 32 seconds, with 1,523 packages and 637 MB recorded in the dependency summary. The raw install tail says "Done in 16.3s using pnpm v11.22.0"; that message covers a narrower interval than the harness's approximately 32-second install step. The framework repository build completed successfully in 28 seconds.

These measurements do not establish starter-app size, production build duration, request latency, deployment success, or an installed-binary check. No application workload or security audit result was recorded.

The test command stopped before Vitest

The recorded command chain was pnpm test:prepare && vitest run && pnpm test:types && pnpm typecheck. Fixture preparation failed after a nested pnpm nuxt prepare invocation reported SIGABRT. The overall test step exited with code 1 after 20 seconds without timing out.

Because preparation failed, the later commands in that chain did not execute. The supplied output establishes no passed, failed, or skipped individual test counts. Its empty stderr and stdout containing undefined plus the recursive-exec error do not explain the abort. This is an incomplete test run, not evidence of failing test assertions or a diagnosis of a framework defect.

For contributors, the useful next step is to follow the contribution guide, including Corepack, pnpm install --frozen-lockfile, and pnpm dev:prepare, then rerun preparation with full logs. The monorepo includes core, schema, module tooling, and Vite, webpack, and Rspack builder packages. Application adopters should evaluate a starter separately from this contributor workflow.

Two reported deployment cases deserve targeted checks

Issue 36150 reports missing nonce attributes with Nuxt 4.5.2, experimental SSR streaming, and nuxt-security@2.6.0. The reporter says nonce extraction happens before the render:html hook where a module injects the value. The supplied extract shows the issue open. This is a reported integration problem, not a security finding from our sandbox or evidence that every Nuxt rendering mode is affected. If that combination matters to your application, inspect the generated scripts and browser CSP results in the exact configuration you plan to deploy.

Issue 36136 reports different chunk contents receiving the same filename across builds, with stale cached assets causing integrity failures. Its history records closure through #36198 on August 28, 2026, followed by reopening on September 15. A September commenter reports a remaining CSS dependency case with Nuxt 4.5.2, Vite 8.3.0, rolldown 1.2.8, and nuxt-security 2.6.0. These are reporter observations, not our reproduced results, and the supplied thread does not establish a general fix.

For an application using long-lived asset caching and subresource integrity, compare filename-to-content mappings across two builds and test returning visitors through the intended cache configuration. Our successful framework build did not perform that check.

How to make the adoption decision

Prototype a representative route with its actual data source, rendering mode, modules, and deployment target. Check where code executes, which responses may be cached, and how the deployed application behaves after an update. Nuxt's advertised range of rendering modes is a reason to evaluate it; compatibility with a particular application still needs verification.

Next.js is a relevant alternative when React is already the team's choice: its README describes full-stack applications built by extending React. SvelteKit is relevant when considering the Svelte ecosystem and its adapter packages. The supplied sources support those roles, not a performance or reliability ranking between frameworks.

What the scores mean

Scores are editorial assessments of the supplied evidence, not measured product quality or an average recommendation. The rubric is: 1 means substantial documented obstacles; 2 means limited evidence for the category; 3 means a documented route with material limits on verification; 4 means several directly supported strengths with remaining gaps; 5 requires broad, directly verified evidence. Missing evidence lowers confidence rather than proving poor quality.

Setup receives 3/5 because installation and the repository build completed, while test preparation did not. Documentation receives 3/5 because the contribution extract supplies concrete setup and test commands, but this review did not inspect the full documentation. Community receives 2/5 because the supplied release and issue discussions show participation without measuring adoption or support responsiveness. Maturity receives 3/5 because the v4.5.2 patch notes document maintenance, while our development checkout and incomplete test run cannot establish production reliability.

Choose Nuxt for a trial when Vue and its integrated conventions fit the project. Use that trial to resolve application and deployment questions that this repository run leaves open.

Alternatives

ProjectWhat it isPick it when
Next.js gh↗A framework for full-stack web applications built on React.Consider Next.js when React is the team's chosen component framework. Its README explicitly describes full-stack applications built by extending React.
SvelteKit gh↗A web development project in the Svelte ecosystem with deployment adapter packages.Consider SvelteKit when evaluating a Svelte project and its deployment options. Its repository lists adapters for Node, static output, Cloudflare, Netlify, and Vercel; this review did not compare their behavior.

Sources

  1. Nuxt README
  2. Nuxt contribution guide
  3. Nuxt v4.5.2 release
  4. Nuxt chunk hash issue 36136
  5. Nuxt SSR streaming nonce issue 36150

More web reviews