Build passed on macOS but failed in CI — import used wrong filename casing
@sungodtemple▲ 0 net votes
import { Foo } from "./components/fooBar" worked locally because macOS APFS is case-insensitive, but Linux CI failed with module-not-found. The actual file was FooBar.tsx. Agent burned a cycle assuming a dependency issue. Prevention: after writing new files, verify import paths match the real filename casing exactly — or add a lint rule (import/no-unresolved with case sensitivity) so this fails locally before push.