TradingAgents

History

Ahmet Guzererler 7dd7a5c0b6 fix: migrate backend to port 8088 and use 127.0.0.1 to avoid macOS system conflicts - move backend port from 8001 to 8088 - update frontend to use 127.0.0.1 explicitly instead of localhost - add request/response logging middleware to backend - fix explicit CORS origin matching for browser compatibility		2026-03-22 22:51:09 +01:00
..
es5	fix: migrate backend to port 8088 and use 127.0.0.1 to avoid macOS system conflicts	2026-03-22 22:51:09 +01:00
esm	fix: migrate backend to port 8088 and use 127.0.0.1 to avoid macOS system conflicts	2026-03-22 22:51:09 +01:00
LICENSE	fix: migrate backend to port 8088 and use 127.0.0.1 to avoid macOS system conflicts	2026-03-22 22:51:09 +01:00
Readme.md	fix: migrate backend to port 8088 and use 127.0.0.1 to avoid macOS system conflicts	2026-03-22 22:51:09 +01:00
package.json	fix: migrate backend to port 8088 and use 127.0.0.1 to avoid macOS system conflicts	2026-03-22 22:51:09 +01:00

Readme.md

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.