Enable noUncheckedIndexAccess#1065
Merged
Merged
Conversation
One of the two most important TypeScript rules, imo. Accessing indexed types (maps, arrays, etc.) in JavaScript doesn't ever throw an out of bounds error, but it might return `undefined` - and TypeScript by default doesn't check against this because so much JavaScript code in the world is written sloppily enough that checking this by default would make it hard to port to TypeScript.
EzraBrooks
force-pushed
the
enable-noUncheckedIndexedAccess
branch
from
07c1080 to
5d7ba93
Compare
bjsowa
approved these changes
Nov 13, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One of the two most important TypeScript rules, imo.
Accessing indexed types (maps, arrays, etc.) in JavaScript doesn't ever throw an out of bounds error, but it might return
undefined- and TypeScript by default doesn't check against this because so much JavaScript code in the world is written sloppily enough that checking this by default would make it hard to port to TypeScript.