Skip to content

chore(deps): update eslint #833

chore(deps): update eslint

chore(deps): update eslint #833

Triggered via pull request December 13, 2025 00:39
Status Success
Total duration 2m 29s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors
tests: runtime/logging/NewRelicLoggingService.js#L165
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
tests: runtime/logging/NewRelicLoggingService.js#L153
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
tests: runtime/logging/NewRelicLoggingService.js#L138
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
tests: runtime/babel.config.js#L1
A `require()` style import is forbidden
tests: runtime/auth/AxiosJwtTokenService.js#L71
Prefer using an optional chain expression instead, as it's more concise and easier to read
tests: runtime/auth/AxiosJwtAuthService.js#L337
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
tests: runtime/auth/AxiosJwtAuthService.js#L233
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
tests: runtime/auth/AxiosJwtAuthService.js#L226
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
tests: runtime/auth/AxiosCsrfTokenService.js#L37
Prefer using nullish coalescing operator (`??=`) instead of an assignment expression, as it is simpler to read
tests: runtime/analytics/SegmentAnalyticsService.js#L30
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator