Vite+ Beta

Original Article ↗ Hacker News Discussion ↗

Vite+ scope and use cases

  • Built on Vite, so it inherits Vite’s browser-focused model and limitations.
  • People are successfully using Vite (and Vite+) for Node targets: NestJS servers, CLIs, and lambdas, often with plugins like vite-plugin-node.
  • For CLIs you don’t use the dev server, but still benefit from linting, formatting, task running, and caching.

Toolchain integration and “boring stack” debate

  • Vite+ bundles Vite, Vitest, Rolldown, tsdown, Oxlint, and Oxfmt into one coherent toolchain.
  • Many see this as the emerging “boring but works” stack: established conventions, rewritten in Rust for speed, and made interoperable.
  • Others argue a truly “boring” stack would need fewer tools and less indirection overall.

Performance, DX, and Node/TypeScript workflow

  • Vite dev builds and HMR are praised, but some report simpler flows (esbuild + manual refresh) being faster for basic apps.
  • Vitest is described as very fast and featureful, but some users find it slower than Jest in large, complex graphs; performance is context-dependent.
  • There’s extensive discussion of running TypeScript on Node: tsx, node --strip-types, custom ESM loaders, and the pain around ESM imports and extension handling.

Complexity, dependencies, and security

  • Several comments criticize the “layer on layer” nature of modern web dev and package sprawl in the Node ecosystem.
  • Some teams are aggressively reducing dependencies, even forgoing third-party packages and relying on AI-assisted bespoke code.
  • Precompilation in CI is seen as safer than running complex dev tooling (like tsx) in production.

Version churn and stability

  • Vite’s many major versions (3–8) are cited as excessive churn and a warning sign for extending this model across the toolchain.
  • Others report migrations as trivial (often just a few config tweaks) and say the gains, especially around SSR, were worth it.

Branding, monetization, and ownership

  • The “+” name and marketing style suggest “subscription tier” to some, causing wariness.
  • Thread notes that Vite+ is MIT-licensed and that the company behind it was acquired by Cloudflare; prior monetization attempts were dropped.
  • Concern remains about tools that try to manage runtimes and become “the whole platform,” with fears of future lock-in or “enshittification.”

Alternatives and ecosystem context

  • Comparisons made to uv (Python), Bun, Deno, Laravel, Rails, ASP.NET Razor + htmx, etc., reflecting a broader search for simpler, more stable stacks.
  • Question about Astro compatibility goes unanswered in the thread (unclear).