ChatGPT解决这个技术问题 Extra ChatGPT

tsconfig.json: Build:No inputs were found in config file

I have an ASP.NET core project and I'm getting this error when I try to build it:

error TS18003: Build:No inputs were found in config file 'Z:/Projects/client/ZV/src/ZV/Scripts/tsconfig.json'. Specified 'include' paths were '["**/*"]' and 'exclude' paths were '["../wwwroot/app","node_modules/*"]'.
1>         The command exited with code 1.
1>       Done executing task "VsTsc" -- FAILED.

This is my tsconfig.json file:

{
  "compileOnSave": true,
  "compilerOptions": {
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "lib": [ "es5", "dom" ],
    "module": "commonjs",
    "moduleResolution": "node",
    "noEmitOnError": true,
    "noImplicitAny": false,
    "outDir": "../wwwroot/app/",
    "removeComments": false,
    "sourceMap": true,
    "target": "es6"
  },
  "exclude": [
    "../wwwroot/app",
    "node_modules/*"
  ]
}

Is this a bug or am I doing something wrong? I did recently upgrade Visual Studio 2015 to update 3. Has anyone encountered this before?

This is intended behavior. You need to have something to compile.
@AluanHaddad You state this as if it is fact. Can you please provide proof for your assertion.
Your source should be where you're pointing in "include" on tsconfig
The default tsconfig.json doesn't have "include" and "exclude" props, so I had to add both. For some reason it seems that both were required

C
Community

Add an empty typescript file to the typescript scripts folder (the location of your tsconfig file) to satisfy the typescript compiler.


what does this mean?
@Christian Matthew This means, you need to add a t least one typescript file to the folder where your app is to satisfy typescript compiler.
What do you mean by script folder. Can you please elaborate more??
Ironcially.. i used this answer a long time ago (added the tsconfig and it fixed this issue). When I added Vue to the project the issue popped up again... so I had to then delete the tsconfig I added in the past, and it worked :P
Thanks. Working for me. But can anyone explain what's actually happening behind?
d
desoga

You can also try to restart your code editor. That works well too.


This worked for me, Eclipse + CodeMix plugin. Thanks.
Works for VSC. You can just restart the TS Server in VSC. Thanks.
I was pulling my hair until I tried this :)
F
FrostyDog

This can occur because typescript server can't find any files described by the include array:

// tsconfig.json
{
  //...
  "include": [
    "./src/"
  ],
}

If you're using VSCode, you can restart your TS server within your editor super easily to prompt it to re-evaluate the file like this:

Navigate to any .ts or .tsx file Open the command palette (CMD + SHIFT + P on mac) Run the TypeScript: Restart TS server command:


How do you get the TypeScript command? I only have e.g. File, Git, GitLens, etc
@Leo make sure you're viewing a .js/.jsx/.ts/.tsx file when you look for the command. The command, for example, is not available when you're viewing an .html file
restarting the ts server did it for me, didn't know that was a thing, thanks
this worked for me, others did not help as I did have .ts files there
This is the best answer, since it describes more in depth why the issue occurs (specific reference to tsconfig.json) and includes the case where the editor is bugging out. +1
T
TreeAndLeaf

I'm not using TypeScript in this project at all so it's quite frustrating having to deal with this. I fixed this by adding a tsconfig.json and an empty file.ts file to the project root. The tsconfig.json contains this:

{
  "compilerOptions": {

    "allowJs": false,
    "noEmit": true // Do not compile the JS (or TS) files in this project on build

  },
  "compileOnSave": false,
  "exclude": [ "src", "wwwroot" ],
  "include": [ "file.ts" ]
}

This can also be used for jsconfig.js. I am not using TS as well, but Vue and Vetur are starting to require this for some reason. That is a really bad architecture on their part.
S
Susampath

If you are using the vs code for editing then try restarting the editor.This scenario fixed my issue.I think it's the issue with editor cache.


P
Pran Kumar Sarkar

When you create the tsconfig.json file by tsc --init, then it comments the input and output file directory. So this is the root cause of the error.

To get around the problem, uncomment these two lines:

"outDir": "./", 
"rootDir": "./", 

Initially it would look like above after un-commenting.

But all my .ts scripts were inside src folder. So I have specified /src.

"outDir": "./scripts", 
"rootDir": "./src", 

Please note that you need to specify the location of your .ts scripts in rootDir.


C
Corey Cole

I have all of my .ts files inside a src folder that is a sibling of my tsconfig.json. I was getting this error when my include looked like this (it was working before, some dependency upgrade caused the error showing up):

"include": [
    "src/**/*"
],

changing it to this fixed the problem for me:

"include": [
    "**/*"
],

d
double-beep

I was getting this error:

No inputs were found in config file 'tsconfig.json'.

Specified include paths were '["**/*"]' and exclude paths '["**/*.spec.ts","app_/**/*.ts","**/*.d.ts","node_modules"]'.

I had a .tsconfig file, which read TS files from the ./src folder.

The issue here was that with the source folder not containing any .ts files and I was running tslint. I resolved issue by removing tslint task from my gulp file, as I don't have any .ts files to be compiled and linted.


r
rose specs

Changing index.js to index.ts fixed this error for me. (I did not have any .ts files before this).

Note: remember to change anywhere you reference index.js to index.ts except of course, where you reference your main file. By convention this is probably in your lib or dist folders. My tsconfig.json:

{
  "compilerOptions": {
    "target": "es2016",
    "module": "commonjs",
    "outDir": "./dist",
    "strict": true,
    "esModuleInterop": true,
    "inlineSourceMap": true,
    "noImplicitAny": false
  }
}

My outDir is ./dist so I reference my main in my package.json as "main": "dist/index.js"

https://i.stack.imgur.com/n26rD.png


N
Nikhil Nayyar

In modern typescript config just set "allowJs" and no need to add any empty .ts file in include directories such as "src" (specified in include array)

tsconfig.json

{
  "compilerOptions": {
    "allowJs": true,
   ...
  },
  "include": [
    "src"
  ]
}

This works well, and for someone who is still getting errors after following the above, just restart your IDE and that shall fix the error.
F
FDisk
"outDir"

Should be different from

"rootDir"

example

    "outDir": "./dist",
    "rootDir": "./src", 

G
Gru

You need to have the root index.tsx or index.ts file for the tsc command to work.


N
NicoJuicy

I added the following in the root ( visual studio )

{
  "compilerOptions": {
    "allowJs": true,
    "noEmit": true,
    "module": "system",
    "noImplicitAny": true,
    "removeComments": true,
    "preserveConstEnums": true,
    "sourceMap": true
  },
  "include": [
    "**/*"
  ],
  "exclude": [
    "assets",
    "node_modules",
    "bower_components",
    "jspm_packages"
  ],
  "typeAcquisition": {
    "enable": true
  }
}

Just an empty "exclude": [ "" ] works too (to override the default which is ./)
M
Matt Parkins

The solution that worked for me was to add a ./ before each include path in the config file:

"include": ["./src/**/*.d.ts", "./src/**/*.js", "./src/**/*.svelte"]

佚名

When using Visual Studio Code, building the project (i.e. pressing Ctrl + Shift + B), moves your .ts file into the .vscode folder (I don't know why it does this), then generates the TS18003 error. What I did was move my .ts file out of the .vscode folder, back into the root folder and build the project again.

The project built successfully!


it puts the .tsconfig file into the .vscode folder. If you move it out of the .vscode folder, you may also need to edit .vscode/tasks.json to point to the new location
R
Rajat Kumar

add .ts file location in 'include' tag then compile work fine. ex.

"include": [
"wwwroot/**/*" ]

B
Big Rich

Ok, in 2021, with a <project>/src/index.ts file, the following worked for me:

If VS Code complains with No inputs were found in config file... then change the include to…

"include": ["./src/**/*.ts"]

Found the above as a comment of How to Write Node.js Applications in Typescript


R
RubbelDieKatz

If you don't want TypeScript compilation, disable it in your .csproj file, according to this post.

Just add the following line to your .csproj file:

<TypeScriptCompileBlocked>true</TypeScriptCompileBlocked>

C
Cosmin

I had to add the files item to the tsconfig.json file, like so:

{
    "compilerOptions": {
        "target": "es5",
        "module": "commonjs",
        "sourceMap": true,
    },
    "files": [
        "../MyFile.ts"
    ] 
}

More details here: https://www.typescriptlang.org/docs/handbook/tsconfig-json.html


i
il0v3d0g

My VSCode was giving me the squiggly line at the beginning of my tsconfig.json file, and had the same error, so

I made sure I had at least one .ts file in the folder specified in the "include" paths (one of the folders in the include path was empty and it was fine) I simply closed the VSCode and opened it back up, and that fixed it. (sigh..)

My folder structure

    tsconfig.json
    package.json
    bar/
         myfile.ts
    lib/
         (no file)

My tsconfig.json

   "compilerOptions": { ... },
   "include": [
    "bar/**/*",
    "lib/**/*"
   ],
   "exclude": [
    ".webpack/**/*",
    ".vscode/**/*"
   ]
   

T
Tha Brad

Btw, just had the same problem.

If you had my case, then you probably have the tsconfig.json not in the same directory as the .ts file.

(In my case I stupidly had next to launch.json and tasks.json inside the .vscode folder :P)


E
Elroy Flynn

I had existing tsconfig files for 4 existing projects in my solution. After upgrading to vs2017 I experienced this problem. It was fixed by adding the (supposedly default) include and exclude sections to the files, as described by NicoJuicy.


S
Sammy

For anyone experiencing the same error should try adding "node modules" to the exclude options

{
   "compilerOptions": {
     ...
   },
   "include": [
      "./src/**/*.ts"
   ],
   "exclude": [
      "./out.d.ts",
      "node_modules",
   ]
}

u
user764754

I have a tsconfig.json file that doesn't apply to any .ts files. It's in a separate folder. Instead I only use it as a base for other tsconfig files via "extends": "../Configs/tsconfig.json". As soon as I renamed the base config file to something else e.g. base-tsconfig.json (and updated the extends statements) the error went away and the extending still worked.


B
Bakhtiiar Muzakparov

I got the same error and in my case it was because vscode couldn't recognize .ts file.

It was seeing it as text file and I had to rename it to remove one letter and add it back to make it work.


L
Laurence73

I ran into this issue constantly while packing my projects into nugets via Visual Studio 2019. After looking for a solution for ages I seem to have solved this by following advice in this article

MSBuild & Typescript

especially part about <TypeScriptCompile /> where I included all my .ts resources with the Include operator and excluded others such as node_modules with the Remove operator. I then deleted the tsconfig.json file in each offending project and the nuget packages were generated and no more errors


c
chadiusvt

I received this same error when I made a backup copy of the node_modules folder in the same directory. I was in the process of trying to solve a different build error when this occurred. I hope this scenario helps someone. Remove the backup folder and the build will complete.


D
Dharman

I had the same error because I had this:

"include": [ 
    "wwwroot/ts/*.ts" 
  ],
  "exclude": [ 
    "node_modules",
    "wwwroot"
  ]

The error appear because the folder wwwroot appear in include and exclude, you should quit one of them.


M
Mostafa Saadatnia

Make sure all your files has a correct name.


d
danilo

You need to have two folders, one for the source (typescript) and another for the output (javascript).

tsconfig.json:

{
  "compilerOptions": {
...
    "outDir": "out/", 
    "rootDir": "src/", 
...

In my case adding the rootDir attribute worked to get ride of the error. VS2022 + Micorosoft.TypeScript.MSBuild 4.6.4. tsconfig.json in root of ASP.NET Core Web Project. Incude, exclude, typeRoots Attributes where already there and the error kept on comming, until rootDir was added.

关注公众号,不定期副业成功案例分享
Follow WeChat

Success story sharing

Want to stay one step ahead of the latest teleworks?

Subscribe Now