Error: Can not read tsconfig.json
See original GitHub issueHi.
Error when trying to deploy with Now
Error: Error: Can not read tsconfig.json from /zeit/76c49dc
at Object.prepareTypescriptEnvironment (/zeit/350a8cf112e00538/.build-utils/.builder/node_modules/@nuxtjs/now-builder/lib/typescript.js:20:19)
https://github.com/JHyeok/jaebook-client/tree/now-sh
source has tsconfig.json.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:20 (7 by maintainers)
Top Results From Across the Web
214 - Stack Overflow
Parsing error: Cannot read file 'd:\test\testproject\tsconfig.app.eslint.json'.eslint One of the major issues I faced here because of the ...
Read more >Parsing error: Cannot read file tsconfig.json, when it's ... - GitHub
Hi, I have nested subprojects, with individual esling and tsconfig configurations, which get parsed correctly from command line, but not ...
Read more >ESLint complains about parsing error and file not matching ...
The project is located in a WSL2 environment. For example: \\wsl$\Ubuntu-20.04\home\<me>\projects\web. In tsconfig.json, I have these as well, ...
Read more >Node.js – Parsing error: Cannot read file '…/tsconfig.json'.eslint
By default, the project s (in parserOptions ) are resolved relative to the current working directory. If you run eslint in a different...
Read more >Documentation - What is a tsconfig.json - TypeScript
By invoking tsc with no input files, in which case the compiler searches for the tsconfig.json file starting in the current directory and...
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
@wobsoriano Looks like you have a trailing comma in that JSON.
@phischdev Make sure your
tsconfig.json
is valid (e.g. no comments), for me it fixed the issue. In mytsconfig.json
I had a comment in the first line for some reason. I removed it and the build succeeded.I hope it helps 😉