src/bin/conditional-test.js   A
last analyzed

Complexity

Total Complexity 3
Complexity/F 1.5

Size

Lines of Code 27
Function Count 2

Duplication

Duplicated Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
wmc 3
eloc 17
mnd 1
bc 1
fnc 2
dl 0
loc 27
rs 10
bpm 0.5
cpm 1.5
noi 2
c 0
b 0
f 0

1 Function

Rating   Name   Duplication   Size   Complexity  
A conditional-test.js ➔ main 0 18 3
1
import { spawn, execSync } from 'child_process';
2
import path from 'path';
3
import {
4
    getTestCommand,
5
    getPrepareCommands
6
} from '../utils';
7
8
async function main() {
9
    const { platform, versions } = process;
10
11
    console.log(JSON.stringify({ platform, versions }));
0 ignored issues
show
Debugging Code introduced by
console.log looks like debug code. Are you sure you do not want to remove it?
Loading history...
12
    // eslint-disable-next-line security/detect-non-literal-require
13
    const packageJSON = require(path.join(process.cwd(), 'package.json'));
14
    const config = packageJSON['node-package-tester'];
15
    const testCommand = getTestCommand(config, { platform, versions });
16
    const prepareCommands = getPrepareCommands(config, { platform, versions });
17
18
    for (const prepareCommand of prepareCommands) {
19
        execSync(prepareCommand);
20
    }
21
22
    const childProcess = spawn('npm', [ 'run', testCommand ], { shell: true, stdio: 'inherit' });
23
24
    childProcess.on('exit', (code) => process.exit(code));
0 ignored issues
show
Compatibility Debugging Code Best Practice introduced by
Use of process.exit() is discouraged as it will potentially stop the complete node.js application. Consider quitting gracefully instead by throwing an Error.
Loading history...
25
}
26
27
main();
28
29