Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

TypeScript auto configure #8324

Closed
fire015 opened this issue Aug 11, 2019 · 1 comment · Fixed by #8332 · May be fixed by NOUIY/next.js#317, NOUIY/next.js#353 or NOUIY/next.js#369
Closed

TypeScript auto configure #8324

fire015 opened this issue Aug 11, 2019 · 1 comment · Fixed by #8332 · May be fixed by NOUIY/next.js#317, NOUIY/next.js#353 or NOUIY/next.js#369
Assignees
@Timer
Milestone
9.0.4

Comments

@fire015
Copy link

fire015 commented Aug 11, 2019

Bug report

Describe the bug

Following the docs, when an empty tsconfig.json file is in the root running next dev throws the following error after installing the typescript packages:

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

To Reproduce

touch tsconfig.json
npm run dev
# Install the packages as recommended
npm run dev

Expected behavior

The tsconfig.json file should be auto-configured with default values as per the docs.

System information

  • macOS 10.14.5
  • Next 9.0.3
  • @types/node: 12.7.1
  • @types/react: 16.9.1
  • typescript: 3.5.3
@Timer Timer added this to the 9.0.4 milestone Aug 12, 2019
@Timer Timer self-assigned this Aug 12, 2019
Timer added a commit to Timer/next.js that referenced this issue Aug 12, 2019
@Timer
Fix TypeScript setup with empty file
25179ae 
New versions of TypeScript now throw an error when no matching TypeScript files are found. We still want to setup in this case.

-----

Closes vercel#8324
@Timer Timer mentioned this issue Aug 12, 2019
Merged
timneutkens pushed a commit that referenced this issue Aug 12, 2019
@Timer @timneutkens
Fix TypeScript setup with empty file (#8332)
ab0384d 
New versions of TypeScript now throw an error when no matching TypeScript files are found. We still want to setup in this case.

-----

Closes #8324
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Timer Timer

Labels
None yet
Projects
None yet
Milestone
9.0.4
3 participants
@fire015 @Timer @balazsorban44