Skip to content

Fix: process.exitCode is being set to an object instead of a number #472

Fix: process.exitCode is being set to an object instead of a number

Fix: process.exitCode is being set to an object instead of a number #472

Triggered via pull request July 3, 2024 21:55
@eLyiNeLyiN
opened #164
master
Status Failure
Total duration 38s
Artifacts

nodejs.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 2 warnings
build (20.x): sources/advanced/Cli.ts#L1
Property 'code' does not exist on type 'never'.
build (20.x)
Process completed with exit code 2.
build (18.x)
The job was canceled because "_20_x" failed.
build (18.x): sources/advanced/Cli.ts#L1
Property 'code' does not exist on type 'never'.
build (18.x)
Process completed with exit code 2.
build (20.x)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-node@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build (20.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/