Skip to content

tsc says "No inputs were found" when "outDir": "." #41734

@benmccann

Description

@benmccann

TypeScript Version: Tested with both 4.1.2 and 4.2.0-dev.20201130

Search Terms:

"No inputs were found"

Code

I get an error message about "No inputs were found" if I have the below in my tsconfig.json. This is extremely confusing because the inputs are indeed present at the location mentioned in the error message

	"compilerOptions" : {
		"outDir": "."
	},

tsc completes successfully if I change the outDir:

	"compilerOptions" : {
		"outDir": "dist"
	},
// A *self-contained* demonstration of the problem follows...
// Test this by running `tsc` on the command-line, rather than through another build tool such as Gulp, Webpack, etc.

Expected behavior:

Ideally tsc should complete successfully and output the .js, .js.map, and .ts.d files alongside my input .ts files. Or if that's something that's not supported then it should tell me that "outDir": "." is not valid or give some other error message is more understandable and actionable

Actual behavior:

TypeScript prints:

No inputs were found in config file 'tsconfig.json'. Specified 'include' paths were '["**/*"]' and 'exclude' paths were '["./"]'.

This is completely wrong. The input is indeed at the given location, so I was tearing my hair out trying to figure out what was wrong

Playground Link: I'm not that familiar with the Playground, but it doesn't look like I can control outDir there, so this probably can't be reproduced there

Related Issues: N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    Working as IntendedThe behavior described is the intended behavior; this is not a bug

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions