persona-community-5/.pnpm-store/v3/files/ba/dd7679d835dea591bf7fff3e32cdd5c03b9b914e970dc001dd9451d0766fcb5b135e8f4372d38ce54d806b613bd7c51d11e8aca0834bb102894e73367a1558
rdev-worker a1d0d1bf1c
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
build: /implement-feature community-ui --requirements 'Build the React commu...
2026-02-24 08:22:30 +00:00

40 lines
871 B
Plaintext

## detect-node
> This is a fork of `detect-node`.
Differences:
- uses named export {isNode}
- has d.ts integrated
- supports ESM
### Install
```shell
npm install --save detect-node-es
```
### Usage:
```diff
-var isNode = require('detect-node');
+var {isNode} = require('detect-node-es');
if (isNode) {
console.log("Running under Node.JS");
} else {
alert("Hello from browser (or whatever not-a-node env)");
}
```
The check is performed as:
```js
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) {}
```
Thanks to Ingvar Stepanyan for the initial idea. This check is both **the most reliable I could find** and it does not use `process` env directly, which would cause browserify to include it into the build.