Skip to content

Enable noUncheckedIndexedAccess: true in tsconfig #499

Enable noUncheckedIndexedAccess: true in tsconfig

Enable noUncheckedIndexedAccess: true in tsconfig #499

Triggered via push April 27, 2026 18:34
Status Failure
Total duration 1m 19s
Artifacts

push.yml

on: push
Lint, build, and test
1m 14s
Lint, build, and test
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
Lint, build, and test: src/cramFile/slice/index.ts#L629
This assertion is unnecessary since it does not change the type of the expression
Lint, build, and test: src/cramFile/slice/index.ts#L627
This assertion is unnecessary since it does not change the type of the expression
Lint, build, and test: src/cramFile/slice/index.ts#L626
This assertion is unnecessary since it does not change the type of the expression
Lint, build, and test: src/cramFile/slice/index.ts#L625
This assertion is unnecessary since it does not change the type of the expression
Lint, build, and test: src/cramFile/slice/index.ts#L302
This assertion is unnecessary since the receiver accepts the original type of the expression
Lint, build, and test: src/cramFile/slice/index.ts#L302
Confusing combination of non-null assertion and assignment like `a! = b`, which looks very similar to `a != b`
Lint, build, and test: src/cramFile/slice/index.ts#L300
Use a `for-of` loop instead of this `for` loop
Lint, build, and test: src/cramFile/codecs/huffman.ts#L205
This assertion is unnecessary since it does not change the type of the expression
Lint, build, and test: src/cramFile/codecs/huffman.ts#L205
Confusing combination of non-null assertion and equality test like `a! == b`, which looks very similar to `a !== b`
Lint, build, and test: src/craiIndex.ts#L28
This assertion is unnecessary since it does not change the type of the expression
Lint, build, and test
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, mymindstorm/setup-emsdk@v14, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/