</>PackageGraphPackageGraph

detect-node-es

npmv1.1.0TypeScript

Detect Node.JS (as opposite to browser environment). ESM modification

Not recommended for new projects

No — detect-node-es should not be adopted for new projects. Last published 1953 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 1953 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 3.1 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 detect-node-es to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

3.1 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

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 detect-node-es README.

jsFull README ↗
module.exports = false;

// Only Node.JS has a process variable that is of [[Class]] process
try {
 module.exports = Object.prototype.toString.call(global.process) === '[object process]' 
} catch(e) {}

detect-node-es vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
detect-node-esthis page01MIT5 years ago
resolve220.7M2MIT2 hours ago
supports-preserve-symlinks-flag124.1M1MIT2 hours ago
axios113.9M4MIT2 hours ago
supports-hyperlinks35.1M1MIT2 hours ago
@expo/package-manager7.5M1MIT2 hours ago

Used by

Popular packages that depend on detect-node-es.

use-sidecarnpm

Sidecar code splitting utils

↓ 65M/wk◈ 1 dependents⚖ MITTS

Relationship graph

Dependencies (left) and dependents (right) of detect-node-es.

use-sidecardetect-node-es
detect-node-es dependencies dependents

Frequently installed together

reactnpm

React is a JavaScript library for building user interfaces.

↓ 159.7M/wk◈ 82 dependents⚖ MIT
@types/reactnpm

TypeScript definitions for react

↓ 138.7M/wk◈ 71 dependents⚖ MITTS
react-domnpm

React package for working with the DOM.

↓ 0/wk◈ 47 dependents⚖ MIT

Release history

No releases in the last two years.

Recent versions of detect-node-es
VersionPublishedSizeLicense
1.1.0latest5 years ago3.1 KBMIT
1.0.06 years ago3.1 KBISC

Overview

detect-node-es is an npm package that detect Node.JS (as opposite to browser environment). ESM modification. It has 1 known dependents in the graph. The latest version is 1.1.0, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need detect Node.JS (as opposite to browser environment). ESM modification 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).
  • Zero runtime dependencies — minimal footprint.

Cons

  • No significant drawbacks detected from available metadata.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

kashey

Keywords

detectnode

Frequently asked questions

Should I use detect-node-es?

No — detect-node-es should not be adopted for new projects. Last published 1953 days ago.

How do I install detect-node-es?

Run `npm install detect-node-es` to add detect-node-es to your npm project.

What license is detect-node-es released under?

detect-node-es is distributed under the MIT license.

How popular is detect-node-es?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on detect-node-es.

Is detect-node-es still maintained?

The most recent release of detect-node-es (v1.1.0) was published 5 years ago.

Does detect-node-es run install scripts?

No. detect-node-es does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.