Gathering detailed insights and metrics for node-auto-run
Gathering detailed insights and metrics for node-auto-run
Gathering detailed insights and metrics for node-auto-run
Gathering detailed insights and metrics for node-auto-run
easy-stack
Simple JS stack with auto run for node and browsers
js-queue
Simple JS queue with auto run for node and browsers
@node-ipc/js-queue
Simple JS queue with auto run for node and browsers
auto-set-node-version
automatically set node version (based on package.json), when 'npm start' command is run.
npm install node-auto-run
Typescript
Module System
Min. Node Version
Node Version
NPM Version
62.9
Supply Chain
89.6
Quality
71.9
Maintenance
100
Vulnerability
100
License
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
13 Commits
2 Branches
1 Contributors
Updated on Apr 15, 2019
Latest Version
0.0.3
Package Id
node-auto-run@0.0.3
Unpacked Size
7.36 kB
Size
2.58 kB
File Count
4
NPM Version
6.9.0
Node Version
10.10.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Starts node projects automatically and keeps checking for them. Starts the projects again if they get crashed. Keeps checking for newly added projects in config file.
Usage: (as Module)
var autoRun = require("node-auto-run");
var runner = new autoRun(config);
Usage: (as standalone node project)
git clone https://github.com/animatedcreativity/node-auto-run
cd node-auto-run
npm update
npm start
You can save a config file node-auto-proxy.js
in parent folder of this node project as explained below.
config
config.js
file in module itself for loading default options. But, this will get overwritten if you update the module.node-auto-proxy.js
file with config options in the current/parent folders of the module, so that config does not get overwritten each time you upgrade the module. Please check: https://www.npmjs.com/package/node-file-configAll config options are optional. Example config:
{
start: false,
interval: 30000,
checks: 2,
projects: {
...
}
}
Example config with projects:
{
start: false,
interval: 30000,
checks: 2,
projects: {
"<project-folder-1>": "<project-name-1>",
"<project-folder-2>": "<project-name-2>",
"<project-folder-3>": "<project-name-3>"
}
}
Methods:
Can be used if you run this as a module.
All methods return promises.
.exec(projectFolder)
runner.exec("<project_folder>");
projectFolder
..processes()
var list = runner.processes();
.process(projectFolder)
var process = runner.process("<project_folder>");
projectFolder
, if its running..config()
var config = runner.config();
config
section above. Useful to get if config is changed in the files.Fun part: what if the node project of this module itself gets crashed?
It will be good if you run this module as a standalone node project. Make 2 copies of the same module's node project and add each other into their config's project list. Or you can keep single configuration file for both, please check config
section above. Start just one copy as it will take care of everything else.
Command to start:
nohup npm start --prefix /root/projects/node/node-auto-run /root/projects/node/node-auto-run 2>/dev/null 1>/dev/null &
Yes, project folder is passed 2 times.
First is prefix to start project from that folder.
Second is argument to tell that the project is running.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
no SAST tool detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/13 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
license file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More