How to fix 'forceConsistentCasingInFileNames' is not set, but 'paths' config is used in TypeScript

What this error means

This warning appears when your tsconfig.json contains a `paths` configuration for module path mapping, but the `forceConsistentCasingInFileNames` compiler option is not explicitly set to true. TypeScript issues this warning because path mapping can be particularly sensitive to file casing issues across different operating systems. The `forceConsistentCasingInFileNames` option ensures that when TypeScript resolves module imports, the casing of the import statement must match the actual file casing on disk. This is critical when using path aliases because: 1. **Windows and macOS** have case-insensitive file systems - `import "./Utils"` and `import "./utils"` both work 2. **Linux** has a case-sensitive file system - incorrect casing causes runtime errors 3. **Path mapping** (`paths` config) performs additional resolution that can amplify casing mismatches When you use path aliases like `@components/*` without this safeguard, code that works on Windows might break when deployed to a Linux production server. TypeScript recommends enabling this option whenever path mapping is used to catch these issues during development.

Typical symptoms

• Warning message about forceConsistentCasingInFileNames and paths config appears during compilation
• Code compiles successfully on Windows/macOS but fails on Linux servers
• Imports work locally but break in CI/CD pipelines running on Linux
• Inconsistent behavior between developers using different operating systems
• Build warnings mentioning file name casing conflicts
• IDE shows no errors but production builds fail with module resolution issues

Common causes

1. The paths compiler option is configured but forceConsistentCasingInFileNames is missing or set to false
2. Using a tsconfig.json template that doesn't include forceConsistentCasingInFileNames by default
3. Inheriting from a base tsconfig (using extends) that doesn't enforce consistent casing
4. Manually adding path aliases without updating other related compiler options
5. Upgrading TypeScript version that introduced stricter validation for path mappings
6. Migrating from JavaScript to TypeScript without reviewing all recommended compiler options

How to fix "'forceConsistentCasingInFileNames' is not set, but 'paths' config is used"

{
  "compilerOptions": {
    "forceConsistentCasingInFileNames": true,
    "baseUrl": "./src",
    "paths": {
      "@components/*": ["components/*"],
      "@utils/*": ["utils/*"],
      "@lib/*": ["lib/*"]
    }
  }
}

npx tsc --noEmit

// WRONG - file is actually "Button.tsx"
import { Button } from "@components/button";

// CORRECT - matches actual file casing
import { Button } from "@components/Button";

// WRONG - folder is actually "utils"
import { formatDate } from "@Utils/date";

// CORRECT
import { formatDate } from "@utils/date";

# Kill any running TypeScript processes
pkill -f "tsserver"

# Restart your development server
npm run dev

{
  "compilerOptions": {
    "forceConsistentCasingInFileNames": true,
    "baseUrl": "./src",
    "paths": {
      "@components/*": ["components/*"],
      "@utils/*": ["utils/*"]
    }
  }
}

{
  "extends": "./tsconfig.base.json",
  "compilerOptions": {
    "baseUrl": "./src",  // Use absolute path or ensure correct casing
    "forceConsistentCasingInFileNames": true
  }
}

name: Type Check
on: [push, pull_request]
jobs:
  typecheck:
    runs-on: ubuntu-latest  # Use Linux to catch casing issues
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: '18'
      - run: npm ci
      - run: npx tsc --noEmit

typecheck:
  image: node:18
  script:
    - npm ci
    - npx tsc --noEmit

Advanced notes

File name 'C:/Project/src/...' differs from already included file name
'c:/Project/src/...' only in casing

{
  "compilerOptions": {
    // Module resolution
    "moduleResolution": "bundler",  // or "node16" for Node.js
    "baseUrl": "./src",
    "paths": {
      "@/*": ["./*"]
    },

    // Strict type checking
    "strict": true,
    "noImplicitAny": true,
    "strictNullChecks": true,

    // Cross-platform compatibility
    "forceConsistentCasingInFileNames": true,
    "esModuleInterop": true,
    "skipLibCheck": true,

    // Output
    "target": "ES2020",
    "module": "ESNext",
    "lib": ["ES2020", "DOM"]
  },
  "include": ["src/**/*"],
  "exclude": ["node_modules", "dist"]
}

npm install -D eslint-plugin-import

// .eslintrc.json
{
  "plugins": ["import"],
  "rules": {
    "import/no-unresolved": "error"
  },
  "settings": {
    "import/resolver": {
      "typescript": {
        "alwaysTryTypes": true
      }
    }
  }
}

# On Unix-like systems
find src -name "*.ts" -o -name "*.tsx"

# Look for duplicates that differ only in casing
find src -type f | sort -f | uniq -i -d

npx tsc --traceResolution > resolution.log
grep -i "casing" resolution.log

git config core.ignorecase false

// find-casing-issues.js
const { execSync } = require('child_process');
const output = execSync('npx tsc --noEmit 2>&1', { encoding: 'utf-8' });
const casingErrors = output.match(/differs.*only in casing/g);
console.log(`Found ${casingErrors?.length || 0} casing issues`);

Frequently asked questions

What does "'forceConsistentCasingInFileNames' is not set, but 'paths' config is u" mean?

json contains a paths configuration for module path mapping, but the forceConsistentCasingInFileNames compiler option is not explicitly set to true. TypeScript issues this warning because path mapping can be particularly sensitive to file casing issues across different operating systems. The forceConsistentCasingInFileNames option ensures that when TypeScript resolves module imports, the casing of the import statement must match the actual file casing on disk.

How do I fix "'forceConsistentCasingInFileNames' is not set, but 'paths' config is u"?

This TypeScript warning occurs when using path mapping in tsconfig.json without enabling forceConsistentCasingInFileNames. While not a critical error, it can lead to cross-platform issues on case-insensitive file systems like Windows and macOS. Enable forceConsistentCasingInFileNames to ensure consistent file casing across all platforms.

What causes "'forceConsistentCasingInFileNames' is not set, but 'paths' config is u"?

The paths compiler option is configured but forceConsistentCasingInFileNames is missing or set to false Using a tsconfig.json template that doesn't include forceConsistentCasingInFileNames by default Inheriting from a base tsconfig (using extends) that doesn't enforce consistent casing

Is the "'forceConsistentCasingInFileNames' is not set, but 'paths' config is u" error serious?

It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Related errors

• Function expression requires a return type

  Function expression requires a return type

  MEDIUM

• src/index.ts is not under 'rootDir'

  How to fix 'file is not under rootDir' error in TypeScript

  MEDIUM

• Function lacks ending return statement and return type does not include 'undefined'

  Function lacks ending return statement and return type does not include 'undefined'

  MEDIUM

• Cannot extend with union type containing 'never'

  How to fix 'Cannot extend with union type containing never' in TypeScript

  MEDIUM

• Cannot find name 'process'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node` and then add 'node' to the types field in your tsconfig.

  How to fix "Cannot find name 'process'" in TypeScript

  MEDIUM

• Module has no exported member 'X'

  How to fix 'Module has no exported member X' error in TypeScript

  MEDIUM

Official resources & further reading

• 📚TypeScript Official Documentation
• 📖
  TypeScript TSConfig - forceConsistentCasingInFileNames(Official Docs)
• 📖
  TypeScript TSConfig Reference(Official Docs)
• 🐙
  TypeScript Issue #17617 - forceConsistentCasingInFileNames with paths(GitHub)
• 🐙
  TypeScript Issue #28769 - Path mapping breaks forceConsistentCasingInFileNames(GitHub)
• 🐙
  TypeScript Issue #50544 - Node16 moduleResolution casing issue(GitHub)
• webhint - TypeScript Consistent Casing