is-node-process
npmv1.2.0TypeScriptReliably determines if the code is running in Node.js
Not recommended for new projects
No — is-node-process should not be adopted for new projects. Last published 1266 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 1266 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 5.8 KB 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 is-node-process 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
- No constraint declared
- Module format
- ESM + CommonJS
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the is-node-process README.
// any/code.js
const { isNodeProcess } = require('is-node-process')
isNodeProcess() // true/falseDependencies
Declared by is-node-process v1.2.0. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (10)
Used by
Popular packages that depend on is-node-process.
Low-level network interception library for Node.js.
Seamless REST/GraphQL API mocking library for browser and Node.js.
Environment-agnostic, ESM-friendly logger for simple needs.
Relationship graph
Dependencies (left) and dependents (right) of is-node-process.
Frequently installed together
Next generation testing framework powered by Vite
Type-safe implementation of invariant with positionals.
TypeScript definitions for node
An HTTP/1.1 client, written from scratch for Node.js
Promise based HTTP client for the browser and node.js
Fast, unopinionated, minimalist web framework
A JavaScript implementation of many web standards
A light-weight module that brings Fetch API to node.js
HTTP and HTTPS modules that follow redirects.
node.js realtime framework server
Happy DOM is a JavaScript implementation of a web browser without its graphical user interface. It includes many web standards from WHATWG DOM and HTML.
A high-level API to automate web browsers
Release history
No releases in the last two years, typically about 4 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.2.0latest | 3 years ago | 5.8 KB | MIT |
| 1.1.0 | 3 years ago | 3.2 KB | MIT |
| 1.0.1 | 5 years ago | 2.7 KB | MIT |
| 1.0.0 | 5 years ago | 2.6 KB | MIT |
Overview
is-node-process is an npm package that reliably determines if the code is running in Node.js. It has 3 known dependents in the graph. The latest version is 1.2.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need reliably determines if the code is running in Node.js and value a focused solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.
Pros
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use is-node-process?
No — is-node-process should not be adopted for new projects. Last published 1266 days ago.
How do I install is-node-process?
Run `npm install is-node-process` to add is-node-process to your npm project.
What license is is-node-process released under?
is-node-process is distributed under the MIT license.
How popular is is-node-process?
npm does not publish download counts. Within PackageGraph's crawl, 3 known packages depend on is-node-process.
Is is-node-process still maintained?
The most recent release of is-node-process (v1.2.0) was published 3 years ago.
Does is-node-process run install scripts?
No. is-node-process does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.