Security News
ESLint is Now Language-Agnostic: Linting JSON, Markdown, and Beyond
ESLint has added JSON and Markdown linting support with new officially-supported plugins, expanding its versatility beyond JavaScript.
The envinfo npm package is a tool that generates information about the development environment. It can be used to report system information, software versions, and configuration details, which is particularly useful for debugging and issue reporting in software projects.
System Information
This command prints information about the system, such as OS, CPU, Memory, and Shell.
envinfo --system
Browsers
This command lists installed web browsers and their versions.
envinfo --browsers
Languages
This command shows the installed languages and their versions, like Node.js, Python, Ruby, etc.
envinfo --languages
Utilities
This command provides information about installed utilities like Git, Make, GCC, etc.
envinfo --utilities
Servers
This command reports on server software like Apache, Nginx, and IIS.
envinfo --servers
Virtualization
This command lists virtualization tools like Docker, Parallels, and VirtualBox.
envinfo --virtualization
IDEs
This command shows the installed Integrated Development Environments (IDEs) and their versions.
envinfo --ides
SDKs
This command lists the installed SDKs for platforms like iOS, Android, and .NET.
envinfo --sdks
Custom Configuration
This command allows for custom configuration to include duplicate packages in the output and the full dependency tree.
envinfo --duplicates --fullTree
The systeminformation package provides detailed information about the system hardware and software. It offers a broader range of system metrics compared to envinfo, but it does not focus on the development environment configuration.
The os package is a core Node.js module that provides basic operating system-related utility functions. It is more limited in scope compared to envinfo and does not provide information about software versions or development tools.
The which package is a simple utility to find the path of the executable files in the system. It is much more specific in functionality compared to envinfo, which provides a comprehensive report of the environment.
Reporting issues is a pain. Responding to issues is a pain. Make it a bit better.
Install this package globally:
npm install -g envinfo || yarn global add envinfo
envinfo
|| npx envinfo
System:
OS: macOS High Sierra 10.13
CPU: x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Free Memory: 3.99 GB
Total Memory: 16.00 GB
Binaries:
Node: 8.9.4
Yarn: 1.3.2
npm: 5.6.0
Watchman: 4.9.0
Docker: 17.12.0-ce, build c97c6d6
Homebrew: 1.5.2
IDEs:
Android Studio: Not Found
Atom: 1.23.3
VSCode: 1.19.3
Sublime Text: Build 3143
Xcode: Xcode 9.0 Build version 9A235
Languages:
Bash: 3.2.57(1)-release
Go: 1.9.3
PHP: 7.1.7
Python: 2.7.10
Ruby: 2.3.3p222
Browsers:
Chrome: 63.0.3239.132
Chrome Canary: 66.0.3333.0
Firefox: 57.0.1
Firefox Developer Edition: 57.0
Firefox Nightly: 58.0a1
Safari: 11.0
Safari Technology Preview: 11.1
--clipboard - Optionally copy directly to your clipboard with envinfo --clipboard
. This feature uses Clipboardy
--packages - Optionally return packages from your package.json: takes either boolean or comma delimited string in CLI or array via API
envinfo --packages minimist,which
System:
OS: macOS High Sierra 10.13
CPU: x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Free Memory: 4.01 GB
Total Memory: 16.00 GB
Binaries:
Node: 8.9.4
Yarn: 1.3.2
npm: 5.6.0
...
Packages:
minimist: ^1.2.0 => 1.2.0
which: ^1.2.14 => 1.3.0
Or all of your packages like this:
envinfo --packages
System:
OS: macOS High Sierra 10.13
CPU: x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Free Memory: 4.01 GB
Total Memory: 16.00 GB
Binaries:
Node: 8.9.4
Yarn: 1.3.2
npm: 5.6.0
...
Packages:
array-includes: ^3.0.3 => 3.0.3
clipboardy: ^1.2.2 => 1.2.2
glob: ^7.1.2 => 7.1.2
...
minimist: ^1.2.0 => 1.2.0
object.entries: ^1.0.4 => 1.0.4
object.values: ^1.0.4 => 1.0.4
os-name: ^2.0.1 => 2.0.1
which: ^1.2.14 => 1.3.0
System:
OS: macOS High Sierra 10.13
CPU: x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Free Memory: 4.01 GB
Total Memory: 16.00 GB
Binaries:
Node: 8.9.4
Yarn: 1.3.2
npm: 5.6.0
...
Global Packages:
envinfo: 4.0.0-beta.1
exp: 48.0.2
lerna: 2.7.1
npm: 5.6.0
npm-check-updates: 2.14.0
react-native-cli: 2.0.1
System:
OS: macOS High Sierra 10.13
CPU: x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Free Memory: 4.01 GB
Total Memory: 16.00 GB
Binaries:
Node: 8.9.4
Yarn: 1.3.2
npm: 5.6.0
...
Packages:
minimist: ^1.2.0 => 1.2.0 (1.2.0, 0.0.8)
System:
OS: macOS High Sierra 10.13
CPU: x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Free Memory: 4.01 GB
Total Memory: 16.00 GB
Binaries:
Node: 8.9.4
Yarn: 1.3.2
npm: 5.6.0
...
Packages:
...
minimatch: 3.0.4
minimist: ^1.2.0 => 1.2.0 (1.2.0, 0.0.8)
mkdirp: 0.5.1
...
envinfo is live in:
react-native info
)create-react-app --info
)exp diagnostics
)solidarity report
)PRs for additional features are welcome! Run npm run lint && npm run format
before committing.
This project came out of a PR to the React Native CLI tool - issues are reported frequently without important environment information, like Node/npm versions.
FAQs
Info about your dev environment for debugging purposes
The npm package envinfo receives a total of 10,723,363 weekly downloads. As such, envinfo popularity was classified as popular.
We found that envinfo demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
ESLint has added JSON and Markdown linting support with new officially-supported plugins, expanding its versatility beyond JavaScript.
Security News
Members Hub is conducting large-scale campaigns to artificially boost Discord server metrics, undermining community trust and platform integrity.
Security News
NIST has failed to meet its self-imposed deadline of clearing the NVD's backlog by the end of the fiscal year. Meanwhile, CVE's awaiting analysis have increased by 33% since June.