envinfo
npmv7.21.0Info about your dev environment for debugging purposes
Safe to adopt
Yes — envinfo scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 287 days ago. 9 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- BMaintenance: grade B, Good.
Last published 287 days ago. 9 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 164 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 2 maintainers, and a contained dependency surface.
- 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 envinfo to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- node >=4
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the envinfo README.
import envinfo from 'envinfo';
envinfo.run(
{
System: ['OS', 'CPU'],
Binaries: ['Node', 'Yarn', 'npm'],
Browsers: ['Chrome', 'Firefox', 'Safari'],
npmPackages: ['styled-components', 'babel-plugin-styled-components'],
},
{ json: true, showNotFound: true }
).then(env => console.log(env));envinfo vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| envinfothis page | 0 | 2 | MIT | 9 months ago |
| path-key | 244.9M | 1 | MIT | 1 day ago |
| env-paths | 0 | 2 | MIT | 1 day ago |
| is-inside-container | 0 | 2 | MIT | 1 day ago |
| strip-json-comments | 0 | 2 | MIT | 1 day ago |
| getenv | 0 | 7 | MIT | 1 day ago |
Dependencies
Declared by envinfo v7.21.0. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (29)
Used by
Popular packages that depend on envinfo.
This package is part of the [React Native CLI](../../README.md). It contains commands for diagnosing and fixing common Node.js, iOS, Android & React Native issues.
DevTools for Vite (work in progress)
Relationship graph
Dependencies (left) and dependents (right) of envinfo.
Frequently installed together
Native-ESM powered web dev build tool
Universal filesystem path utils
Smooth scrolling for any amount of data
Structured diagnostic code library
Framework for building one portable devtool integration that runs in any viewer.
Vite DevTools Kit
<!-- automd:badges color=yellow codecov bundlephobia packagephobia -->
Graphical primitives for visualization, such as lines and areas.
Floating UI for the web
JavaScript parser and stringifier for YAML
This package is part of the [React Native CLI](../../README.md). It contains commands for managing the Android part of React Native app.
The semantic version parser used by npm.
Release history
8 releases in the last two years, typically about 24 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 7.21.0latest | 9 months ago | 164 KB | MIT |
| 7.20.0 | 10 months ago | 164 KB | MIT |
| 7.19.0 | 10 months ago | 163 KB | MIT |
| 7.18.0 | 11 months ago | 162 KB | MIT |
| 7.17.0 | 11 months ago | 161 KB | MIT |
| 7.16.1 | 11 months ago | 161 KB | MIT |
| 7.16.0 | 11 months ago | 161 KB | MIT |
| 7.15.0 | 11 months ago | 158 KB | MIT |
| 7.14.0 | 2 years ago | 158 KB | MIT |
| 7.13.0 | 2 years ago | 158 KB | MIT |
| 7.12.0 | 2 years ago | 157 KB | MIT |
| 7.11.1 | 2 years ago | 158 KB | MIT |
| 7.11.0 | 2 years ago | 158 KB | MIT |
| 7.10.0 | 3 years ago | 158 KB | MIT |
| 7.9.0 | 3 years ago | 157 KB | MIT |
Overview
envinfo is an npm package that info about your dev environment for debugging purposes. It has 2 known dependents in the graph. The latest version is 7.21.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need info about your dev environment for debugging purposes and value a focused solution.
When not to use it
Consider an alternative if you need to minimize your dependency tree, 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).
Cons
- Large dependency tree (29 direct dependencies) increases install size and audit surface.
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Frequently asked questions
Should I use envinfo?
Yes — envinfo scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 287 days ago. 9 releases in the last 2 years.
How do I install envinfo?
Run `npm install envinfo` to add envinfo to your npm project.
What license is envinfo released under?
envinfo is distributed under the MIT license.
How popular is envinfo?
npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on envinfo.
Is envinfo still maintained?
The most recent release of envinfo (v7.21.0) was published 9 months ago.
Does envinfo run install scripts?
No. envinfo does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.