chore: clarify benchmark count output #352
onmaxAnnotations
10 errors and 1 warning
|
CI
Process completed with exit code 1.
|
|
CI:
benchmarks/worker.ts#L466
Unexpected console statement. Only these console methods are allowed: warn, error
|
|
CI:
benchmarks/worker.ts#L463
Unexpected console statement. Only these console methods are allowed: warn, error
|
|
CI:
benchmarks/worker.ts#L462
Unexpected console statement. Only these console methods are allowed: warn, error
|
|
CI:
benchmarks/worker.ts#L442
Unexpected console statement. Only these console methods are allowed: warn, error
|
|
CI:
benchmarks/worker.ts#L441
Unexpected console statement. Only these console methods are allowed: warn, error
|
|
CI:
benchmarks/worker.ts#L389
`new Array()` is unclear in intent; use either `[x]` or `Array.from({length: x})`
|
|
CI:
benchmarks/worker.ts#L343
Inconsistently quoted property 'pragma' found
|
|
CI:
benchmarks/worker.ts#L339
Inconsistently quoted property 'accept' found
|
|
CI:
benchmarks/worker.ts#L174
`new Error()` is too unspecific for a type check. Use `new TypeError()` instead
|
|
CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|