Bump xo from 0.24.0 to 0.59.2 #583
Triggered via pull request
July 24, 2024 05:22
Status
Failure
Total duration
1d 15h 37m 6s
Artifacts
–
Annotations
12 errors and 3 warnings
test (windows-2019):
main/context-menu.js#L4
Do not use "require".
|
test (windows-2019):
main/context-menu.js#L6
Do not use "module".
|
test (windows-2019):
main/context-menu.js#L6
The variable `func` should be named `function_`. A more descriptive name will do too.
|
test (windows-2019):
main/context-menu.js#L6
The async arrow function should be named.
|
test (windows-2019):
main/context-menu.js#L10
Unexpected use of the global variable 'process'. Use 'require("process")' instead.
|
test (windows-2019):
main/index.js#L2
Use default import for module `path`.
|
test (windows-2019):
main/index.js#L2
Do not use "require".
|
test (windows-2019):
main/index.js#L2
There should be no empty line between import groups
|
test (windows-2019):
main/index.js#L2
Prefer `node:path` over `path`.
|
test (windows-2019):
main/index.js#L5
Do not use "require".
|
test (macos-10.14)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
test (ubuntu-18.04)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
test (windows-2019)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
|
test (windows-2019)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Test
The ubuntu-18.04 environment is deprecated, consider switching to ubuntu-20.04(ubuntu-latest), or ubuntu-22.04 instead. For more details see https://github.com/actions/virtual-environments/issues/6002
|