How to fix Cannot find input files matching pattern in TypeScript

What this error means

The "Cannot find input files matching pattern" error appears when TypeScript's compiler looks for source files to compile but finds none matching the patterns you've specified in your tsconfig.json configuration. This typically happens when: 1. **Incorrect glob patterns**: The patterns in your 'include' array don't match any actual files 2. **Missing files**: The files referenced in your 'files' array don't exist at the specified paths 3. **Wrong directory**: Your tsconfig.json is in the wrong location relative to your source files 4. **Empty project**: There are no .ts/.tsx files in the directories you're trying to include TypeScript needs at least one input file to compile. When it can't find any files matching your configuration, it shows this error to prevent compiling nothing (which would be confusing). This is a configuration issue rather than a code error, and fixing it involves adjusting your tsconfig.json or project structure. The error commonly appears when: - Starting a new TypeScript project with an empty src/ directory - Moving files around without updating tsconfig.json - Using incorrect glob patterns that don't match your file structure - Having typos in file paths or directory names

Typical symptoms

• TypeScript compilation fails with 'Cannot find input files matching pattern'
• Running `tsc` or `npx tsc` shows the error with no further compilation output
• Build tools (webpack, Vite, etc.) fail with TypeScript compilation errors
• IDE may show configuration warnings about missing source files
• Project appears to have no TypeScript files to compile
• Error occurs even with seemingly correct tsconfig.json settings

Common causes

1. Empty 'include' array or patterns that don't match any files
2. 'files' array contains paths to non-existent files
3. tsconfig.json is in wrong directory (not at project root)
4. Source files are in different location than expected
5. File extensions missing from glob patterns (e.g., '**/*' instead of '**/*.ts')
6. Using 'exclude' patterns that accidentally exclude all files
7. Case sensitivity issues in file paths on case-sensitive filesystems
8. Project has no .ts/.tsx files in the included directories
9. Hidden files or directories not being matched by glob patterns
10. Incorrect use of relative paths in 'files' array

How to fix "Cannot find input files matching pattern"

// Example tsconfig.json
{
  "compilerOptions": {
    "target": "es2020",
    "module": "commonjs"
  },
  "include": ["src/**/*.ts", "src/**/*.tsx"]
}

# Check what files match your patterns
# For pattern "src/**/*.ts"
find src -name "*.ts" | head -5

# For pattern "**/*.ts"
find . -name "*.ts" | head -5

# If no files found, you need to create TypeScript files
# or adjust your patterns

{
  "compilerOptions": { /* ... */ },
  "files": [
    "src/index.ts",
    "src/utils/helpers.ts",
    "src/types.d.ts"
  ]
}

# Check each file in the files array
ls -la src/index.ts
ls -la src/utils/helpers.ts
ls -la src/types.d.ts

# If any file is missing, either:
# 1. Create the missing file
# 2. Remove it from the files array
# 3. Fix the path if it's incorrect

# Create a test directory and file
mkdir -p src
cat > src/test.ts << 'EOF'
// Test TypeScript file
const message: string = "Hello TypeScript";
console.log(message);
EOF

{
  "compilerOptions": {
    "target": "es2020",
    "module": "commonjs",
    "outDir": "./dist"
  },
  "include": ["src/**/*.ts"]
}

npx tsc

# If successful, you should see:
# - No error messages
# - dist/test.js created (if outDir is set)
# - Or test.js in same directory (if no outDir)

# If still failing, the issue is with tsconfig.json location
# or other configuration

# Check current directory and tsconfig location
pwd
ls -la tsconfig.json

# If tsconfig.json is in a subdirectory, TypeScript will look
# for files relative to that subdirectory

# Example structure:
# project/
#   ├── tsconfig.json          # Looking for src/ relative to project/
#   └── src/
#       └── index.ts          # ✓ Found: project/src/index.ts

# WRONG structure:
# project/
#   ├── config/
#   │   └── tsconfig.json    # Looking for src/ relative to config/
#   └── src/
#       └── index.ts         # ✗ Not found: config/src/index.ts doesn't exist

// tsconfig.json at project root
{
  "compilerOptions": {
    "composite": true
  },
  "references": [
    { "path": "./packages/client" },
    { "path": "./packages/server" }
  ]
}

// packages/client/tsconfig.json
{
  "extends": "../../tsconfig.base.json",
  "include": ["src/**/*.ts"]
}

{
  "include": ["src/**/*.ts"],
  "exclude": ["node_modules", "dist", "**/*.test.ts"]
}

{
  "include": ["src/**/*.ts"],
  // "exclude": ["node_modules", "dist"]  // Comment out to test
}

{
  "compilerOptions": {
    "explainFiles": true
  },
  "include": ["src/**/*.ts"]
}

npx tsc --explainFiles

# Output shows:
# - Files being included and why
# - Files being excluded and why
# - Configuration being used
# - Resolution details

# Example output:
# File '/project/src/index.ts':
#   Matched by include pattern '**/*' in 'tsconfig.json'
# File '/project/node_modules/typescript/lib/lib.es5.d.ts':
#   Library code file

npx tsc --traceResolution

Advanced notes

{
  "include": ["src/**/*"]
}

{
  "include": ["src/**/*.ts", "src/**/*.tsx"]
}

{
  "include": ["packages/*/src/**/*.ts"],
  "exclude": ["packages/*/node_modules", "packages/*/dist"]
}

{
  "include": ["src/**/*.ts"],
  "exclude": ["**/*.test.ts", "**/*.spec.ts"]
}

// tsconfig.base.json
{
  "compilerOptions": {
    "strict": true,
    "target": "es2020"
  }
}

// tsconfig.json
{
  "extends": "./tsconfig.base.json",
  "include": ["src/**/*.ts"]
}

// tsconfig.test.json
{
  "extends": "./tsconfig.json",
  "include": ["src/**/*.ts", "tests/**/*.ts"]
}

# Official TypeScript starter
npx tsc --init

# Creates tsconfig.json with common options
# Then create your source files

# Or use a template:
npx create-react-app my-app --template typescript
npx @vitejs/plugin-react my-app --template react-ts

# Create test directory
mkdir ts-test && cd ts-test

# Minimal tsconfig.json
echo '{"include": ["src/**/*.ts"]}' > tsconfig.json

# Minimal source file
mkdir src
echo 'const x: string = "test";' > src/test.ts

# Test compilation
npx tsc

# If this works, gradually add your actual configuration
# until you find what breaks it

Frequently asked questions

What does "Cannot find input files matching pattern" mean?

json configuration. This typically happens when: 1. Incorrect glob patterns: The patterns in your 'include' array don't match any actual files 2.

How do I fix "Cannot find input files matching pattern"?

This TypeScript error occurs when the compiler cannot find any source files matching the patterns specified in your tsconfig.json's 'include' or 'files' properties. The fix involves correcting file patterns, verifying file paths, or adjusting your TypeScript configuration to include the correct source files.

What causes "Cannot find input files matching pattern"?

Empty 'include' array or patterns that don't match any files 'files' array contains paths to non-existent files tsconfig.json is in wrong directory (not at project root)

Is the "Cannot find input files matching pattern" error serious?

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

Related errors

• Cannot narrow type with instanceof for built-in types

  How to fix 'Cannot narrow type with instanceof for built-in types' error in TypeScript

  MEDIUM

• The inferred type of this node exceeds the maximum length the compiler will serialize

  How to fix "The inferred type of this node exceeds the maximum length the compiler will serialize" in TypeScript

  MEDIUM

• Interface declaration cannot declare a class field

  How to fix "Interface declaration cannot declare a class field" in TypeScript

  MEDIUM

• Index signature in type 'X' only permits reading

  How to fix 'Index signature in type only permits reading' 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 - include(Official Docs)
• 📖
  TypeScript TSConfig - files(Official Docs)
• 📖
  TypeScript TSConfig - exclude(Official Docs)
• 📖
  TypeScript Handbook - tsconfig.json(Official Docs)
• TypeScript Tutorial - tsconfig.json Guide
• Stack Overflow - TypeScript tsconfig Questions
• Khalil Stemmler - Understanding tsconfig.json
• 🐙
  TypeScript GitHub - Cannot Find Input Files Issues(GitHub)