</>PackageGraphPackageGraph

client-only

npmv0.0.1

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

Not recommended for new projects

No — client-only should not be adopted for new projects. Last published 1468 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 1468 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 611 B installed.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding client-only to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

611 B
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
No constraint declared
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

client-only vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
client-onlythis page02MIT4 years ago
react152.8M82MIT1 day ago
react-dom143.7M47MIT1 day ago
react-style-singleton59.1M2MIT1 day ago
reselect44M1MIT1 day ago
next40.6M0MIT1 day ago

Used by

Popular packages that depend on client-only.

styled-jsxnpm

Full CSS support for JSX without compromises

↓ 0/wk◈ 1 dependents⚖ MITTS
expo-routernpm

Expo Router is a file-based router for React Native and web applications.

↓ 0/wk◈ 2 dependents⚖ MITTS

Relationship graph

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

styled-jsxexpo-routerclient-only
client-only dependencies dependents

Frequently installed together

react-native-screensnpm

Native navigation primitives for your React Native app.

↓ 0/wk◈ 1 dependents⚖ MITTS
react-native-reanimatednpm

More powerful alternative to Animated library for React Native.

↓ 0/wk◈ 4 dependents⚖ MITTS
@testing-library/react-nativenpm

Simple and complete React Native testing utilities that encourage good testing practices.

↓ 0/wk◈ 10 dependents⚖ MITTS
react-server-dom-webpacknpm

React Server Components bindings for DOM using Webpack. This is intended to be integrated into meta-frameworks. It is not intended to be imported directly.

↓ 0/wk◈ 2 dependents⚖ MIT
@expo/metro-runtimenpm

Tools for making advanced Metro bundler features work

↓ 0/wk◈ 3 dependents⚖ MITTS
react-native-gesture-handlernpm

Declarative API exposing native platform touch and gesture system to React Native

↓ 0/wk◈ 3 dependents⚖ MITTS
react-native-webnpm

React Native for Web

↓ 0/wk◈ 4 dependents⚖ MIT
@expo/log-boxnpm

Error overlay for universal Expo apps.

↓ 0/wk◈ 4 dependents⚖ MIT
exponpm

The Expo SDK

↓ 0/wk◈ 18 dependents⚖ MITTS
reactnpm

React is a JavaScript library for building user interfaces.

↓ 152.8M/wk◈ 82 dependents⚖ MIT
react-domnpm

React package for working with the DOM.

↓ 143.7M/wk◈ 47 dependents⚖ MIT
@types/reactnpm

TypeScript definitions for react

↓ 0/wk◈ 71 dependents⚖ MITTS

Release history

No releases in the last two years.

Recent versions of client-only
VersionPublishedSizeLicense
0.0.1latest4 years ago611 BMIT

Overview

client-only is an npm package that this is a marker package to indicate that a module can only be used in Client Components. It has 2 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 Client Components and value a focused 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

  • 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.

Maintainers

sebmarkbage

Keywords

react

Frequently asked questions

Should I use client-only?

No — client-only should not be adopted for new projects. Last published 1468 days ago.

How do I install client-only?

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

What license is client-only released under?

client-only is distributed under the MIT license.

How popular is client-only?

npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on client-only.

Is client-only still maintained?

The most recent release of client-only (v0.0.1) was published 4 years ago.

Does client-only run install scripts?

No. client-only does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.