Use case-sensitive-paths-webpack-plugin

[doctorpangloss]

Description

Related to webpack/webpack#5543

This is a fairly frequent source of support tickets at Heroku, because it leads customers to believe that the service is buggy. "Works on my machine"

Case sensitivity of imports causes errors on your Gatsby Cloud environment whereas case insensitive file systems on the user's local machine do not cause the error.

Steps to reproduce

1. Create a file A.js.
2. Create a file b.js.
3. In b.js, add the statement: import * as A from 'a'.
4. Observe this import succeeds on macOS and Windows, but not in your cloud environment.

You can see a production error similar to this here.

Expected result

You probably want to be case sensitive and issue an error using https://github.com/Urthen/case-sensitive-paths-webpack-plugin by bundling that plugin into Gatsby's build process by default.

Actual result

Triggered builds fail for the case sensitivity issue.

Environment

  System:
    OS: Windows 10 10.0.19043
    CPU: (12) x64 AMD Ryzen 5 3600 6-Core Processor              
  Binaries:
    Node: 14.16.1 - C:\Program Files\nodejs\node.EXE
    npm: 6.14.12 - C:\Program Files\nodejs\npm.CMD
  Languages:
    Python: 3.9.5 - /c/Python39/python
  Browsers:
    Edge: Spartan (44.19041.964.0), Chromium (90.0.818.51)
  npmPackages:
    gatsby: ^3.2.1 => 3.2.1 
    gatsby-background-image: ^1.5.2 => 1.5.2 
    gatsby-plugin-brotli: ^2.0.0 => 2.0.0 
    gatsby-plugin-image: ^1.3.0 => 1.3.0 
    gatsby-plugin-react-helmet: ^4.3.0 => 4.3.0 
    gatsby-plugin-sass: ^4.3.0 => 4.3.0 
    gatsby-plugin-sharp: ^3.3.0 => 3.3.0 
    gatsby-plugin-styled-components: ^4.4.0-next.0 => 4.4.0-next.0 
    gatsby-source-filesystem: ^3.3.0 => 3.3.0 
    gatsby-transformer-remark: ^4.0.0 => 4.0.0 
    gatsby-transformer-sharp: ^3.3.0 => 3.3.0 
    gatsby-transformer-yaml: ^3.3.0 => 3.3.0 
  npmGlobalPackages:
    gatsby-cli: 2.12.42