No Inputs were found in config file Error
See original GitHub issueHi there!
The VS Code 1.28.0 on Mac shows the following error innode_modules/protractor/tsconfig.json
:
No inputs were found in config file
'~/projects/myproject/node_modules/protractor/tsconfig.json'.
Specified 'include' paths were '["**/*"]' and 'exclude' paths were
'["built","node_modules","testapp","website","scripts","exampleTypescript","spec/**/*"]'.
Very annoying and makes the proble window show up all the time. Is it something that can be fixed?
- Node Version: 10.11
- Protractor Version: 5.4.1
- Angular Version: 6
- Browser(s): Chrome
- Operating System and Version: Mac High Sierra
Issue Analytics
- State:
- Created 5 years ago
- Comments:28 (8 by maintainers)
Top Results From Across the Web
tsconfig.json: Build:No inputs were found in config file
I was getting this error: No inputs were found in config file 'tsconfig.json'. Specified include paths were '["**/*"]' and exclude paths '["**/*.spec.ts" ...
Read more >No inputs were found in config file in TypeScript | bobbyhadz
The error "No inputs were found in config file" occurs when we try to build a project that does not contain any TypeScript...
Read more >error TS18003: No inputs were found in config file 'tsconfig ...
Are you using tsc to compile your project? Is there a src directory next to your tsconfig.json that contains .ts files?
Read more >"build: no inputs were found in config file" .... tsconfig.json
Error message is not helpful since the inputs do exist as they have not changed unless the meaning of the input parms has...
Read more >TypeScript for JavaScript - Part 1 (Setup) | picostitch
> npm run typecheck > jskatas.org@2.0.0 typecheck /app > tsc error TS18003: No inputs were found in config file '/app/ ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Restarting VSCode fixed this error like a magic in my case.
i got this as well, restarting vs code fixed the issues for me. just in case, someone stumped on this in future and this may help!