Flux.ai was started around 3 years ago in TypeScript with the default compiler settings. If we could go back in time, there is one setting we would surely change: noUncheckedIndexedAccess. By default, this setting is false. Many people believe it should be true.
What does noUncheckedIndexedAccess do? By default, TypeScript assumes any array element or object property you access dynamically actually exists:
In the example above, the function will throw an error if the string is empty, because str[0] returns undefined and doesn't have a toUpperCase function. TypeScript doesn't warn you about that, regardless of whether strict mode is enabled or not. This is a huge hole in type safety.
The flag noUncheckedIndexedAccess will plug that hole and force you to deal with the possible undefined:
So, why can't we just turn on noUncheckedIndexedAccess? You can, but in a large codebase like that of Flux.ai, you are likely to get thousands of type errors. We had 2761 errors across 373 files! For one speedy engineer converting one file every minute, it would have taken 6+ hours of mind-numbing work to convert all 373 files.
The solution we describe here is how to smoothly convert your codebase with some simple heuristics and automation.
According to Wikipedia, a heuristic technique
is any approach to problem solving or self-discovery that employs a practical method that is not guaranteed to be optimal, perfect, or rational, but is nevertheless sufficient for reaching an immediate, short-term goal or approximation.
That is definitely true here.
The goal was to get the codebase compiling with the new flag, not to fix any bugs. The fixing can come later.
To that end, we intentionally added type assertions ! to suppress all new type errors from undefined types without changing the runtime behavior of the code.
Expanding the scope of replacements to preceding lines allowed us then to automate more fixes with few false positives.
The full script we ran on our codebase is below. Note: it did not fix all the errors. It fixed around 2400 out of 2761 errors, leaving around 100 files for us to fix by hand.
Pro-tip: when experimenting with the replacers and precede, you can simply reset your changes with git reset --hard HEAD (assuming you are working in a git repo).

A practical guide to Design for Manufacturing (DFM) that helps hardware teams transition from validated prototypes to scalable, production-ready products.

Practical PCB layout and design strategies to reduce EMI and improve the chances of passing FCC and CE compliance testing on the first attempt.

A guide to evaluating hardware feasibility through requirements definition, component selection, BOM cost estimation, power budgeting, and early manufacturing risk identification.

Learn how to choose the right hardware architecture by comparing the unique engineering priorities of robotics, wearables, and IoT products.

A practical guide to hardware prototyping—from breadboard to custom PCB, through structured testing, verification, validation, and iterative revision.

How electrical, mechanical, and firmware teams can build effective collaboration workflows through design reviews, revision control, and engineering change management.

Avoid costly errors in your PCB design with these expert tips! Discover the 5 most common mistakes in trace width, vias, power planes, and more. Learn how Flux’s AI Copilot helps you catch these issues early, ensuring your board is ready for manufacturing.

Explore the key aspects of PCB thermal analysis and discover best practices for enhancing your PCB design. Understand how thermal conductivity impacts heat management and overall PCB functionality, leading to more reliable and efficient circuits.