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).

Explains how RC low-pass filters attenuate high-frequency signals using a resistor and capacitor, with the cutoff frequency formula, component selection trade-offs, and PCB layout best practices.

Covers how reflow ovens solder SMT components through preheat, soak, reflow, and cooling stages, with common defects and how PCB layout decisions impact manufacturing yield.

Gerber files are the universal 2D vector format that bridges PCB design and fabrication. This guide covers what each layer file contains, how to export and verify a complete manufacturing package, and the common mistakes that cause production delays.

A pi filter is a three-element passive CLC network that provides stronger ripple and EMI suppression than a single capacitor. This guide covers topology selection, component derating, resonance damping, and PCB layout best practices.

Tantalum capacitors offer high capacitance density in a tiny footprint but demand strict polarity and voltage derating. This guide explains how they compare to ceramics and aluminum electrolytics, common failure risks, and how to select and place them safely.

PCBA turns a bare PCB into a functional circuit by mounting and soldering components. This guide breaks down the assembly workflow, SMT vs through-hole methods, required manufacturing files, and common defects to avoid.

ERC checks schematic-level electrical issues while DRC checks PCB layout rules -- engineers run ERC before layout and DRC during or after routing.

The complete hardware design workflow covers requirements, schematic capture, PCB layout, validation, prototyping, and manufacturing.