How to fix Composite projects may not ask for all files in TypeScript

TypeScriptINTERMEDIATEMEDIUM

This error occurs when a TypeScript composite project tries to use compiler options that are incompatible with composite project configuration. The most common cause is conflicting settings between composite mode and skipLibCheck options.

What this error means

TypeScript composite projects are designed to work as part of a monorepo build system, where project references are resolved in a specific order. When you enable the `composite` option in a `tsconfig.json` file, you're telling TypeScript that: 1. This project is part of a larger multi-project setup 2. It should emit `.tsbuildinfo` files for build caching 3. Other projects can reference this project as a dependency The error "Composite projects may not ask for all files" indicates a conflict between what the composite project configuration requires and certain compiler options that would cause TypeScript to process files in ways incompatible with the composite build system. This typically happens when options like `skipLibCheck` are used incorrectly or when the project structure doesn't properly align with composite project constraints.

How to fix "Composite projects may not ask for all files"

1Verify composite configuration

First, confirm that composite is explicitly set to true in your tsconfig.json:

json

{
  "compilerOptions": {
    "composite": true,
    "declaration": true,
    "declarationMap": true,
    "sourceMap": true
  }
}

The declaration, declarationMap, and sourceMap options are required for composite projects.

2Check include and exclude patterns

Ensure your include and exclude arrays are explicit and don't conflict with other projects:

json

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

Avoid using overly broad patterns like ["src"] which might include unintended files. Use exact paths relative to the project root.

3Remove or fix skipLibCheck in composite projects

If you're using skipLibCheck, verify it's compatible with your composite setup:

json

{
  "compilerOptions": {
    "composite": true,
    "skipLibCheck": true
  }
}

If you still get the error, try removing skipLibCheck for the composite project itself:

json

{
  "compilerOptions": {
    "composite": true
  }
}

You can use skipLibCheck in consumer projects that reference this one, but not in the base composite project.

4Verify project references are correct

Check that references in your tsconfig.json point to valid paths with proper tsconfig.json files:

json

{
  "compilerOptions": {
    "composite": true
  },
  "references": [
    { "path": "../utils" },
    { "path": "../types" }
  ]
}

Each referenced project must:
- Have its own tsconfig.json with composite: true
- Contain a src directory or proper include pattern
- Not include files from parent or sibling projects

5Clean build cache and rebuild

Remove build artifacts and cache, then rebuild using --build:

bash

# Remove all .tsbuildinfo files and dist directories
find . -name "*.tsbuildinfo" -delete
find . -name "dist" -type d -exec rm -rf {} + 2>/dev/null || true

# Rebuild using the composite build system
tsc --build tsconfig.json

# Or rebuild with verbose output to see what's happening
tsc --build tsconfig.json --listFiles

6Check TypeScript version consistency

Ensure all projects use the same TypeScript version:

bash

npm list typescript

All projects should use the same major.minor version:

json

{
  "devDependencies": {
    "typescript": "^5.3.0"
  }
}

If versions differ, update them:

bash

npm install -D typescript@latest

How to fix Composite projects may not ask for all files in TypeScript

What this error means

Typical symptoms

Common causes

How to fix "Composite projects may not ask for all files"

Advanced notes

Related errors

Official resources & further reading