server: Change target from ES2018 (Node 10) to ES2022 (Node 18) #1531
Annotations
11 errors and 2 warnings
build (20.x):
test/fixtures/server/valid.js#L62
The 'crypto.verify' is still an experimental feature and is not supported until Node.js 12.0.0. The configured version range is '>=11.0.0'
|
build (20.x):
test/fixtures/server/valid.js#L84
Expected an assignment or function call and instead saw an expression
|
build (20.x)
Process completed with exit code 1.
|
build (18.x)
The job was canceled because "_20_x" failed.
|
build (18.x):
test/fixtures/server/valid.js#L62
The 'crypto.verify' is still an experimental feature and is not supported until Node.js 12.0.0. The configured version range is '>=11.0.0'
|
build (18.x):
test/fixtures/server/valid.js#L84
Expected an assignment or function call and instead saw an expression
|
build (18.x)
Process completed with exit code 1.
|
build (22.x)
The job was canceled because "_20_x" failed.
|
build (22.x):
test/fixtures/server/valid.js#L62
The 'crypto.verify' is still an experimental feature and is not supported until Node.js 12.0.0. The configured version range is '>=11.0.0'
|
build (22.x):
test/fixtures/server/valid.js#L84
Expected an assignment or function call and instead saw an expression
|
build (22.x)
The operation was canceled.
|
build (20.x)
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/
|
build (20.x)
The following actions use a deprecated Node.js version 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/
|