Skip to content

chore: Bump @eslint/plugin-kit from 0.2.0 to 0.2.3 #374

chore: Bump @eslint/plugin-kit from 0.2.0 to 0.2.3

chore: Bump @eslint/plugin-kit from 0.2.0 to 0.2.3 #374

Triggered via pull request November 15, 2024 21:29
Status Success
Total duration 55s
Artifacts

test.yml

on: pull_request
Build and Test
44s
Build and Test
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 10 warnings
Build and Test
Error: Test Error
Build and Test
Error: Test Error
Build and Test: src/common/stdout.spec.ts#L15
'process.stdout' will use Object's default stringification format ('[object Object]') when stringified
Build and Test: src/common/stdout.spec.ts#L17
'process.stdout' will use Object's default stringification format ('[object Object]') when stringified
Build and Test: src/main.ts#L33
Unexpected object value in conditional. The condition is always true
Build and Test: src/main.ts#L33
Unnecessary conditional, value is always truthy
Build and Test: src/main.ts#L48
Unexpected object value in conditional. The condition is always true
Build and Test: src/main.ts#L48
Unnecessary conditional, value is always truthy
Build and Test: src/main/getConfigs.ts#L133
Unexpected nullable string value in conditional. Please handle the nullish/empty cases explicitly
Build and Test: src/main/getConfigs.ts#L133
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
Build and Test: src/main/getConfigs.ts#L133
Unexpected nullable string value in conditional. Please handle the nullish/empty cases explicitly
Build and Test: src/main/getConfigs.ts#L133
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator