Build step hangs at "Checking validity of types .."
See original GitHub issueDescribe the bug
When I run yarn build (or npm run build) on a newly cloned repository, the build process hangs at info - Checking validity of types ... This stops me from deploying the solution to Vercel or any other host.
To Reproduce Steps to reproduce the behavior:
npx degit timlrx/tailwind-nextjs-starter-blog#typescriptyarn installyarn build
Expected behavior The site should build without hanging.
Terminal output
darbio@192-168-1-110 test % npx degit timlrx/tailwind-nextjs-starter-blog#typescript
> cloned timlrx/tailwind-nextjs-starter-blog#typescript
darbio@192-168-1-110 test % yarn install
yarn install v1.22.17
warning ../../../package.json: No license field
info No lockfile found.
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] π Resolving packages...
info There appears to be trouble with your network connection. Retrying...
warning @mailchimp/mailchimp_marketing > superagent@3.8.1: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>.
warning @mailchimp/mailchimp_marketing > superagent > formidable@1.2.6: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
[2/4] π Fetching packages...
[3/4] π Linking dependencies...
warning " > file-loader@6.2.0" has unmet peer dependency "webpack@^4.0.0 || ^5.0.0".
[4/4] π¨ Building fresh packages...
success Saved lockfile.
$ husky install
husky - not a Git repository, skipping hooks installation
β¨ Done in 199.79s.
darbio@192-168-1-110 test % yarn build
yarn run v1.22.17
warning ../../../package.json: No license field
$ next build && node ./scripts/generate-sitemap
info - Checking validity of types ..
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:7 (2 by maintainers)
Top Results From Across the Web
next build stuck on "Checking validity of types" #31994 - GitHub
Describe the Bug. next build keeps getting stuck on " Checking validity of types..." forever. I tried downgrading next's version to 10.1.3 (myΒ ......
Read more >Next Build hangs forever - Stack Overflow
Apparently the build freeze was caused by empty files located all over ... using v8.12.2 and it always keep in "Checking validity of...
Read more >Ignoring TypeScript Errors - next.config.js
js fails your production build ( next build ) when TypeScript errors are present in your project. If you'd like Next.js to dangerously...
Read more >Introduction to the Build Lifecycle - Apache Maven
This command executes each default lifecycle phase in order ( validate , compile , package , etc.), before executing verify .
Read more >Detect and diagnose crashes - Android Developers
An Android app crashes whenever there's an unexpected exit caused by an ... of your daily active users who experienced any type of...
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 Free
Top 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
Thanks @aozaki-kuro. Upgrading typescript to 4.7.0 dev works.
Itβs hard to support all the different package managers (which should not even be affecting the build) and the interaction of the dependencies. In the next contentlayer version, I will probably use yarn as the default and if you are using other package managers, you would just help to do your own checks.
Update:
pnpmseemed to be working fine after updated to 6.32.x TypeScript check no longer hangs