react-clientside-effect

Create components whose prop changes map to a global side effect

react-clientside-effect@1.2.8 was published on 2025-05-18. Its manifest declares 1 runtime dependency and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All react-clientside-effect versions · Permanent reference to 1.2.8

Package specifications

Version1.2.8
License declarationMIT
Published2025-05-18T03:09:46.789Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count1
Peer requirement count1
Optional dependency count0
Minified size930 B
Minified + gzip498 B
Unpacked distribution size16.47 KiB
Published file count7
Package typeNot declared
ES module entrylib/index.es.js
Default entrylib/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies1
Repository stars0
Repository forks4

Install react-clientside-effect 1.2.8

npm install react-clientside-effect@1.2.8
pnpm add react-clientside-effect@1.2.8
yarn add react-clientside-effect@1.2.8

Runtime dependencies

Peer requirements

  • react ^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0 || ^19.0.0-rc

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
Code-Review3/10 — Found 7/23 approved changesets -- score normalized to 3
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness