Building stuck on Linting and checking validity of types ...

[FearTheWild]

Summary

I am trying to deploy a project and build. It all builds fine locally, lints fine locally, but when I try to deploy it gets stuck at Linting and checking validity of types ...

I'm struggling to find errors where I can debug this problem?

Additional information

This is the build log

[15:16:32.707] Running build in Washington, D.C., USA (East) – iad1
[15:16:32.799] Cloning github.com/Medfolioai/medfolio (Branch: main, Commit: fa04f9d)
[15:16:32.839] Skipping build cache, deployment was triggered without cache.
[15:16:33.543] Cloning completed: 743.622ms
[15:16:33.821] Running "vercel build"
[15:16:34.231] Vercel CLI 39.1.1
[15:16:34.579] Warning: Detected "engines": { "node": ">=16.0.0" } in your `package.json` that will automatically upgrade when a new major Node.js Version is released. Learn More: http://vercel.link/node-version
[15:16:34.589] Installing dependencies...
[15:16:39.728] npm warn deprecated superagent@3.8.1: Please upgrade to v9.0.0+ as we have fixed a public vulnerability with formidable dependency. Note that v9.0.0+ requires Node.js v14.18.0+. See https://github.com/ladjs/superagent/pull/1800 for insight. This project is supported and maintained by the team at Forward Email @ https://forwardemail.net
[15:16:40.567] npm warn deprecated formidable@1.2.6: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
[15:16:53.397] 
[15:16:53.398] > cvgen@0.1.0 preinstall
[15:16:53.398] > npx only-allow npm
[15:16:53.398] 
[15:16:54.258] npm warn exec The following package was not found and will be installed: only-allow@1.2.1
[15:16:54.591] 
[15:16:54.592] added 589 packages in 20s
[15:16:54.592] 
[15:16:54.592] 159 packages are looking for funding
[15:16:54.592]   run `npm fund` for details
[15:16:54.618] Detected Next.js version: 13.5.4
[15:16:54.622] Running "npm run build"
[15:16:54.759] 
[15:16:54.759] > cvgen@0.1.0 build
[15:16:54.759] > next build
[15:16:54.759] 
[15:16:55.399] Attention: Next.js now collects completely anonymous telemetry regarding usage.
[15:16:55.399] This information is used to shape Next.js' roadmap and prioritize features.
[15:16:55.399] 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:
[15:16:55.400] https://nextjs.org/telemetry
[15:16:55.400] 
[15:16:55.484]    Linting and checking validity of types ...

Example

No response

[FearTheWild]

This was resolved. It was some strange Windows line endings.

[smartdeveler]

I have same issue.
How can i fix this issue?
I use debian 12.
what is meaning of "Windows line endings"?

[aaron-mota]

I was having this issue recently, successfully building locally with no linting or type-checking errors, yet it would get stuck at Linting and checking validity of types... and just never complete or give me an error message of any kind (it would error because of timing out after ~45min).

This Linting and checking validity of types... step is actually two things: the linting check (ESLint-related) and the type checking (TypeScript-related).

I was able to finally get it to build by updating my next.config.ts to include these two lines, individually turning off each of these steps during builds:

  eslint: { ignoreDuringBuilds: true }, // linting step (ESLint)
  typescript: { ignoreBuildErrors: true }, // type-checking step (TypeScript)

NOTE: Vercel also successfully built & deployed my project by having just one of them at a time, so that may be another alternative (just make sure that whatever one you're ignoring during the build process, you're checking it locally). For me, I could solo out either one, and they'd both successfully build (4.5min when allowing type checking, 7min when allowing linting)... not sure why they don't work well together.

This isn't a super great solution obviously, but you can still do either of these steps locally, or even add it as a little script to do before building locally (which I'm in a habit of building locally before any big code changes anyway), so it works for me.

Otherwise, before making this change, one time mine actually PASSED and built on Vercel at literally 44min and 51sec. So, maybe if you upgrade something with Vercel, it will allow for longer builds, and you can keep the Linting and checking validity of types... step in its entirety then?

More clarity / console.logging about what is actually not working would be great from Vercel, though 🙏