Articles for people who
ship the stack
Original rewrites on React, Node.js, TypeScript and AI — practical notes from the same engineering practice behind our operator software. Article bodies are in English.
Tagged: Vite
Practical notes: Node’s Native Test Runner vs Jest vs Vitest: One Suite, Three
Operable walkthrough of Practical notes: Node’s Native Test Runner vs Jest vs Vitest: One Suite, Three: contracts, checks, and drop-in code slots for teams shipping this pattern.
9 min readVite + TypeScript Is The 2026 Standard: Why You Should Stop
Vite and TypeScript are the 2026 standard for React apps: why Vite over CRA, getting started, a project structure that scales and tsconfig worth setting.
3 min readReact+Vite versus Next.js: pick for the job
React with Vite or Next.js? Routing, SSR, developer experience and deployment shape decide it. Pick for the job instead of cargo-culting one stack everywhere.
5 min readBeginner Guide: Vite First, Then Next.js (Skip New CRA)
CRA, Vite and Next.js compared on setup, dev experience, SEO and learning curve. For new React learners: start with Vite, move to Next.js once routing matters.
4 min readVite + React from zero, with React Compiler enabled early
Vite and React from zero: scaffold the project, read the entry point and folder layout, and enable the React Compiler before the first feature is written.
8 min readReact component tests with Vitest and Testing Library
React component tests with Vitest and Testing Library: wire Vitest into Vite, colocate behavior tests, run watch vs CI, and give AI agents a red-green loop.
3 min readVite 8 merged its bundlers into Rolldown—what broke
Vite 8 defaults to Rolldown for dev and production. Real CJS interop breaks, chunk migration pitfalls, and a safe checklist before you trust green CI.
6 min readJSX is not HTML inside JavaScript — it is a compile step
Plain JavaScript cannot parse angle-bracket UI; JSX is HTML-like syntax rewritten by Babel or Vite into createElement calls before the browser runs it.
4 min readSkip rebuild loops for monorepo packages with conditional exports
Point package.json exports at TypeScript source under a development condition so Vite, Node, and Webpack can HMR shared UI without rebuilding every internal package.
6 min read
About these articles
Request a 24h estimate
Need the same stack in a production operator layer? Send the brief — estimate within 24 hours.