</>PackageGraphPackageGraph

server-only

npmv0.0.1

This is a marker package to indicate that a module can only be used in Server Components.

11.6M
Weekly downloads
1
Dependents
0
Dependencies
87/100
Popularity

Overview

server-only is an npm package that this is a marker package to indicate that a module can only be used in Server Components. It is extremely widely used, with about 11.6M downloads per week and 1 known dependents in the graph. The latest version is 0.0.1, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need this is a marker package to indicate that a module can only be used in Server Components and value a battle-tested, widely-adopted solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Large, well-established user base (11.6M weekly downloads).
  • Clear open-source license (MIT).
  • Zero runtime dependencies — minimal footprint.

Cons

  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Relationship graph

Dependencies (left) and dependents (right) of server-only.

expo-routerserver-only
server-only dependencies dependents

Used by

Popular packages that depend on server-only.

Alternatives to server-only

Frequently installed together

Version history

VersionPublishedLicense
0.0.1latest3 years agoMIT

Maintainers

Keywords

Frequently asked questions

How do I install server-only?

Run `npm install server-only` to add server-only to your npm project.

What license is server-only released under?

server-only is distributed under the MIT license.

How popular is server-only?

server-only has approximately 11,568,264 downloads per week and 1 known dependent packages.