The CLI was incorrectly exiting with code 0 even when linting errors were found, making it impossible for CI/CD systems and scripts to detect when linting issues are present.

Changes Made

• Modified runCMD() function in cmd/tsgolint/cmd.go to return exit code 1 when errorsCount > 0
• Added missing build tag to enablevtprocessing_windows.go to fix compilation on non-Windows systems
• Exit behavior now follows standard linting tool conventions:
  • Exit code 0: No linting errors found (success)
  • Exit code 1: Linting errors found (failure)

Testing

Verified the fix works correctly with manual testing:

# No errors - exits with code 0
$ rslint
Found 0 errors (linted 1 file with 40 rules in 66ms using 2 threads)
$ echo $?
0

# With errors - exits with code 1
$ rslint
no-unsafe-call — Unsafe call of a(n) `any` typed value.
Found 1 error (linted 1 file with 40 rules in 58ms using 2 threads)
$ echo $?
1

Both default and jsonline output formats work correctly. Other CLI modes (help, API, LSP, IPC) remain unaffected.

Fixes #42.

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.