Netlify Build Environment: Case-Sensitivity Discrepancies Between Local OS and Linux Production

Development workflows using netlify dev often occur on macOS or Windows, where the filesystem is case-insensitive. However, Netlify's production build environment utilizes a Linux-based system that strictly enforces case-sensitivity for all file paths and imports.

This architectural difference can lead to scenarios where a project builds and runs successfully in a local environment but fails during the production deploy phase, specifically when importing assets or components with mismatched casing.

Given that netlify.toml standardizes build commands but does not enforce filesystem naming conventions, what are the recommended strategies for detecting these discrepancies before the deployment phase? Is there a configuration within the Netlify CLI to simulate a case-sensitive environment locally?