How to fix Option 'declaration' cannot be used without 'emitDeclarationOnly' when 'noEmit' is set in TypeScript

What this error means

TypeScript's compiler options for file emission fall into distinct categories: - **noEmit**: Disables all output - no .js files, source maps, or declaration files - **emitDeclarationOnly**: Only emits .d.ts declaration files, no JavaScript - **declaration**: Emits both .js and .d.ts files When you have `"noEmit": true` in your configuration, TypeScript doesn't emit anything at all. If you also try to use `"declaration": true` (which requires some form of output), or `"emitDeclarationOnly": true` (which contradicts noEmit by emitting declarations), TypeScript throws error TS5053. This conflict typically arises when: 1. Your tsconfig.json extends a base configuration that sets noEmit 2. You're overriding those settings inconsistently 3. You have conflicting compiler options passed via CLI and config file

Typical symptoms

• TypeScript compilation fails immediately with TS5053 error
• The error appears after updating TypeScript or changing tsconfig.json
• Building or type-checking works in some contexts but fails in others
• You're using a monorepo where tsconfig files extend shared configs
• The error prevents any build process from starting

Common causes

1. Your tsconfig.json sets noEmit: true while also specifying declaration: true or emitDeclarationOnly: true
2. You're extending a base tsconfig (like tsconfig.lib.json) that has conflicting options
3. An extended config has noEmit set, and you're trying to override with emitDeclarationOnly
4. You specified --noEmit on the CLI while your tsconfig has emitDeclarationOnly: true
5. A tool (like tsc --noEmit) is overriding your configuration

How to fix "Option 'declaration' cannot be used without 'emitDeclarationOnly' when 'noEmit' is set"

{
  "compilerOptions": {
    "noEmit": true  // Pick ONE strategy - this disables ALL output
  }
}

{
  "compilerOptions": {
    "emitDeclarationOnly": true,  // Emit only .d.ts files
    "declaration": true
  }
}

{
  "compilerOptions": {
    "declaration": true,  // Emit .d.ts alongside .js
    "noEmit": false       // Explicitly allow emission (or omit, default is false)
  }
}

{
  "compilerOptions": {
    "noEmit": true,
    "emitDeclarationOnly": true  // These conflict!
  }
}

{
  "compilerOptions": {
    "noEmit": true,
    "declaration": true  // This requires output!
  }
}

{
  "compilerOptions": {
    "noEmit": true
  }
}

{
  "compilerOptions": {
    "emitDeclarationOnly": true,
    "declaration": true
  }
}

{
  "extends": "./tsconfig.base.json",
  "compilerOptions": {
    "emitDeclarationOnly": true  // Overrides noEmit from base
  }
}

cat tsconfig.base.json | grep -A5 '"compilerOptions"'

{
  "extends": "./tsconfig.base.json",
  "compilerOptions": {
    "noEmit": false,  // Override inherited noEmit
    "emitDeclarationOnly": true,
    "declaration": true
  }
}

{
  "compilerOptions": {
    "noEmit": true,
    "target": "ES2020",
    "module": "ESNext"
  }
}

{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "noEmit": false,
    "declaration": true,
    "outDir": "./dist"
  },
  "include": ["src/**/*"]
}

# Type check (no output)
tsc --noEmit

# Build (emits .js and .d.ts)
tsc --project tsconfig.build.json

# Check for errors (no output files created)
npx tsc --noEmit

# Or build if using emitDeclarationOnly
npx tsc

Advanced notes

# This conflicts if tsconfig has emitDeclarationOnly
npx tsc --noEmit

# This conflicts if tsconfig has noEmit
npx tsc --emitDeclarationOnly

npx tsc                    # Uses tsconfig.json settings
npx tsc --project tsconfig.build.json  # Uses alternate config

Frequently asked questions

What does "TS5053" mean?

ts files When you have "noEmit": true in your configuration, TypeScript doesn't emit anything at all. If you also try to use "declaration": true (which requires some form of output), or "emitDeclarationOnly": true (which contradicts noEmit by emitting declarations), TypeScript throws error TS5053. This conflict typically arises when: 1.

How do I fix "TS5053"?

This error occurs when TypeScript compiler options conflict in your tsconfig.json file. The declaration option requires either emitDeclarationOnly or a normal emit mode, but noEmit prevents all file emission. The fix involves choosing one option strategy and removing conflicting settings.

What causes "TS5053"?

Your tsconfig.json sets noEmit: true while also specifying declaration: true or emitDeclarationOnly: true You're extending a base tsconfig (like tsconfig.lib.json) that has conflicting options An extended config has noEmit set, and you're trying to override with emitDeclarationOnly

Is the "TS5053" error serious?

Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Related errors

• Declaration merging failed for 'X'

  How to fix "Declaration merging failed for X" in TypeScript

  MEDIUM

• Could not find a declaration file for module 'lodash'

  Could not find a declaration file for module 'lodash'

  MEDIUM

• Decorator 'X' must be used on a class method

  How to fix 'Decorator must be used on a class method' error in TypeScript

  MEDIUM

• Could not find a declaration file for module 'X'

  Could not find a declaration file for module 'X'

  MEDIUM

• Module has no exported member 'X'

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

  MEDIUM

• Argument of type 'undefined' is not assignable to parameter of type 'string'

  How to fix "Argument of type 'undefined' is not assignable to parameter of type 'string'" in TypeScript

  MEDIUM

Official resources & further reading

• 📚TypeScript Official Documentation
• 📖
  TypeScript: TSConfig Option - noEmit(Official Docs)
• 📖
  TypeScript: TSConfig Option - emitDeclarationOnly(Official Docs)
• 📖
  TypeScript: TSConfig Reference - Complete option documentation(Official Docs)
• 🐙
  Allow '--noEmit' to override 'emitDeclarationOnly' from config - GitHub Issue(GitHub)
• Typescript config conflict 'noEmit' and 'emitDeclarationOnly' - GitHub Discussion