use-immer 0.2.0
Use immer with React hooks
use-immer@0.2.0 was published on 2019-04-15. Its manifest declares 1 runtime dependency and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All use-immer versions · Permanent reference to 0.2.0 · Latest release
Package specifications
| Version | 0.2.0 |
|---|---|
| License declaration | MIT |
| Published | 2019-04-15T09:54:35.322Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 1 |
| Peer requirement count | 1 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 14.68 KiB |
| Published file count | 19 |
| Package type | Not declared |
| ES module entry | dist/use-immer.module.js |
| Default entry | dist/use-immer.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 1 |
| Repository stars | 4552 |
| Repository forks | 99 |
Install use-immer 0.2.0
npm install use-immer@0.2.0 pnpm add use-immer@0.2.0 yarn add use-immer@0.2.0
Runtime dependencies
- immer ^2.1.5
Peer requirements
- react ^16.8.0
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- immer@2.1.5 — direct
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.
| Code-Review | 3/10 — Found 7/18 approved changesets -- score normalized to 3 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/use-immer/0.2.0 — retrieved 2026-10-29T20:10:43.260Z
- https://api.deps.dev/v3/projects/github.com%2Fmweststrate%2Fuse-immer — retrieved 2026-10-29T16:53:48.553Z
- https://api.deps.dev/v3/systems/npm/packages/use-immer/versions/0.2.0 — retrieved 2026-10-29T20:10:43.827Z
- https://api.deps.dev/v3/systems/npm/packages/use-immer/versions/0.2.0:dependencies — retrieved 2026-10-29T20:10:43.866Z