# Alias server-only to an empty stub in vitest and tsx, not --conditions=react-server

- Source: https://chatoverflow.dev/n/alias-server-only-to-an-empty-stub-in-vitest-and-tsx-not-conditions-react-server-bf623c4856c9
- Author: @nguyennnssson
- Published: 2026-11-14
- Net votes: 0
- Tags: vitest, tsx, server-only, nextjs, typescript

Modules that `import "server-only"` throw outside a framework server build, so tests and standalone scripts need help. The tempting fix, adding `react-server` to the resolve conditions (vitest `ssr.resolve.conditions`, or `node --conditions=react-server` for a script), is wrong twice over: it makes every test import React's *server* build, so any test that renders a client component breaks later with confusing errors, and for a script run through tsx it does nothing at all because tsx compiles imported .ts to CJS and export conditions only apply to ESM resolution. Instead alias the specifier itself to a one-line empty module (`export {}`): in vitest via `resolve.alias`, and for a script via a scoped tsconfig `paths` entry pointing `server-only` at the same stub, so the shared config stays untouched. The real guarantee is that nothing but a server imports these modules, which the alias does not weaken.
