Why next build stuck on "Checking validity of types..."?

[nelsonlaidev]

When I deploy my next.js project on Vercel or build on local. And stuck on "Checking validity of types...".

info  - Checking validity of types ..

I deploy on vercel for one hour. Then get build failed.
How can I resolve it?

Vercel log:

18:46:15.041 | Cloning github.com/TszHong0411/honghong.me (Branch: dev, Commit: 09f594b)
18:46:15.041 | Cloning completed: 647.557ms
18:46:15.088 | Analyzing source code...
18:46:15.401 | Installing build runtime...
18:46:18.135 | Build runtime installed: 2.733s
18:46:18.846 | Looking up build cache...
18:46:19.314 | Build Cache not found
18:46:19.523 | Running "install" command: `npm install`...
18:46:19.530 | Detected `package-lock.json` generated by npm 7...
18:47:16.304 |  
18:47:16.305 | > [email protected] postinstall
18:47:16.305 | > prisma generate || true
18:47:16.305 |  
18:47:17.560 | Prisma schema loaded from prisma/schema.prisma
18:47:18.844 |  
18:47:18.844 | ✔ Generated Prisma Client (3.9.2 \| library) to ./node_modules/@prisma/client in 102ms
18:47:18.845 | You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
18:47:18.845 | ```
18:47:18.845 | import { PrismaClient } from '@prisma/client'
18:47:18.845 | const prisma = new PrismaClient()
18:47:18.845 | ```
18:47:18.912 |  
18:47:18.912 | > [email protected] prepare
18:47:18.912 | > husky install
18:47:18.912 |  
18:47:19.020 | husky - Git hooks installed
18:47:19.040 |  
18:47:19.040 | added 1368 packages, and audited 1369 packages in 59s
18:47:19.041 |  
18:47:19.041 | 350 packages are looking for funding
18:47:19.041 | run `npm fund` for details
18:47:19.043 |  
18:47:19.043 | found 0 vulnerabilities
18:47:19.085 | Detected Next.js version: 12.1.0
18:47:19.285 | Running "npm run build"
18:47:19.502 |  
18:47:19.502 | > [email protected] build /vercel/path0
18:47:19.502 | > next build
18:47:19.502 |  
18:47:25.478 | Generated 22 documents in .contentlayer
18:47:25.505 | Attention: Next.js now collects completely anonymous telemetry regarding usage.
18:47:25.505 | This information is used to shape Next.js' roadmap and prioritize features.
18:47:25.505 | You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
18:47:25.505 | https://nextjs.org/telemetry
18:47:25.505 |  
18:47:25.568 | info  - Checking validity of types...

Repository: Link
Branch: dev

[thibautsabot]

Hello.

Thank you for providing a link to your repository.
It seems that the issue is in the lib/remark-code-title.ts file.

This simple diff:

allows to go through the typechecking without any issue.

I'm not sure why this is happening, but it should help you debug it 🙂 .

[nelsonlaidev]

Thanks a lot. How did you know this?

[thibautsabot]

I tried to only run typescript (without building the whole app) and then removed some files until the process did not hang anymore.

After few attempts I noticed that deleting the lib folder was working.

More tries led me to this file and this line ^^.

[nelsonlaidev]

got it thanks

[lancejpollard]

How did you "only run typescript", like this (in the top-level project directory)?

tsc --build --verbose

My build is taking 20+ minutes, and is really just hanging for some reason, not quite sure how to debug yet.

[nelsonlaidev]

Try this to do type checking:
tsc --noEmit

[smartdeveler]

not work

[Jsloo]

is the problem solved?
May i know how u solve the prolem?

[smartdeveler]

Not solved

…

On Fri, Mar 21, 2025, 15:04 Jsloo ***@***.***> wrote: is the problem solved? May i know how u solve the prolem? — Reply to this email directly, view it on GitHub <#34803 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL3VALFQHU6IFVUO7EFX3HT2VP2M3AVCNFSM6AAAAABXGBXTASVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENJXGYZDMMQ> . You are receiving this because you commented.Message ID: <vercel/next. ***@***.***>