egutierrez
9661a5ce1f
The SPA (web/) and the web gateway (cmd/webgw) move to a dedicated app projects/message_bus/apps/uniweb (its own Gitea sub-repo). unibus is now strictly the bus plane: membership/keys, the client library and demo peers. uniweb consumes unibus as a Go module via replace => ../unibus. No capability lost; same SPA and gateway, in their own service folder. go build/vet/test green after extraction.
detect-node
This is a fork of
detect-node.
Differences:
- uses named export {isNode}
- has d.ts integrated
- supports ESM
Install
npm install --save detect-node-es
Usage:
-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:
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.